Comment # 8 on bug 1124922 from Oliver Kurz

I am not aware of the problem reproducible in openQA tests. The problem was
reported happening on the openQA *worker* machines, i.e. the machines
*executing* the openQA tests.

I checked on the machine openqaworker1.o.o and found in the service journal of
systemd-remount-fs:

```
-- Reboot --
Nov 24 03:33:33 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Nov 25 03:31:13 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Nov 25 03:33:54 openqaworker1 systemd-remount-fs[784]: mount: /: mount point is
busy.
Nov 25 03:33:54 openqaworker1 systemd-remount-fs[784]: /usr/bin/mount for /
exited with exit status 32.
Nov 25 03:33:54 openqaworker1 systemd[1]: systemd-remount-fs.service: Main
process exited, code=exited, status=1/FAILURE
Nov 25 03:33:54 openqaworker1 systemd[1]: Failed to start Remount Root and
Kernel File Systems.
Nov 25 03:33:54 openqaworker1 systemd[1]: systemd-remount-fs.service: Unit
entered failed state.
Nov 25 03:33:54 openqaworker1 systemd[1]: systemd-remount-fs.service: Failed
with result 'exit-code'.
-- Reboot --
Nov 26 03:34:27 openqaworker1 systemd-remount-fs[793]: mount: /: mount point is
busy.
Nov 26 03:34:27 openqaworker1 systemd-remount-fs[793]: /usr/bin/mount for /
exited with exit status 32.
Nov 26 03:34:27 openqaworker1 systemd[1]: systemd-remount-fs.service: Main
process exited, code=exited, status=1/FAILURE
Nov 26 03:34:27 openqaworker1 systemd[1]: Failed to start Remount Root and
Kernel File Systems.
Nov 26 03:34:27 openqaworker1 systemd[1]: systemd-remount-fs.service: Unit
entered failed state.
Nov 26 03:34:27 openqaworker1 systemd[1]: systemd-remount-fs.service: Failed
with result 'exit-code'.
-- Reboot --
Nov 27 03:33:40 openqaworker1 systemd-remount-fs[801]: mount: /: mount point is
busy.
-- Reboot --
Nov 28 03:34:26 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Nov 29 03:31:20 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Nov 29 03:34:02 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Nov 30 03:31:43 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Nov 30 03:34:26 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Dec 01 03:31:45 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Dec 01 03:34:28 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Dec 03 03:30:21 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Dec 03 03:39:05 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Dec 04 03:31:45 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Dec 04 03:34:27 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Dec 05 03:30:17 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Dec 05 03:39:01 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Dec 05 13:00:50 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Dec 05 13:03:33 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
Dec 05 13:25:25 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File
Systems.
-- Reboot --
Dec 05 13:28:07 openqaworker1 systemd[1]: Started Remount Root and Kernel File
Systems.
lines 179-236/236 (END)
```

so we were either "lucky" since Nov 27 or the problem has gone away recently.
This seems to be supported by the other machines:

```
for i in aarch64 openqaworker1 openqaworker4 power8 imagetester rebel; do echo
$i && ssh root@$i "journalctl -u systemd-remount-fs | grep 'busy' | tail -n 3";
done
aarch64
openqaworker1
Nov 25 03:33:54 openqaworker1 systemd-remount-fs[784]: mount: /: mount point is
busy.
Nov 26 03:34:27 openqaworker1 systemd-remount-fs[793]: mount: /: mount point is
busy.
Nov 27 03:33:40 openqaworker1 systemd-remount-fs[801]: mount: /: mount point is
busy.
openqaworker4
Nov 24 03:34:09 openqaworker4 systemd-remount-fs[797]: mount: /: mount point is
busy.
Nov 26 03:33:44 openqaworker4 systemd-remount-fs[798]: mount: /: mount point is
busy.
Nov 27 03:33:27 openqaworker4 systemd-remount-fs[797]: mount: /: mount point is
busy.
power8
imagetester
rebel
Nov 23 03:32:31 rebel systemd-remount-fs[600]: mount: /: mount point is busy.
Nov 27 03:32:34 rebel systemd-remount-fs[596]: mount: /: mount point is busy.
Nov 28 03:32:31 rebel systemd-remount-fs[601]: mount: /: mount point is busy.
```

are you aware of any recent fixes which could coincide with this timeframe?