https://bugzilla.suse.com/show_bug.cgi?id=1202000 https://bugzilla.suse.com/show_bug.cgi?id=1202000#c2 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #2 from Fabian Vogt <fvogt@suse.com> --- Didn't help, openQA is still unhappy. The journal shows: Aug 05 05:37:34.280907 susetest systemd[1]: Starting Remount Root and Kernel File Systems... ... Aug 05 05:37:34.281179 susetest systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Aug 05 05:37:34.281193 susetest systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. Aug 05 05:37:34.281207 susetest systemd[1]: Failed to start Remount Root and Kernel File Systems. ... Aug 05 05:37:34.247313 susetest systemd-remount-fs[444]: /usr/bin/mount for / exited with exit status 32. Aug 05 05:37:34.282334 susetest apparmor.systemd[435]: Restarting AppArmor Aug 05 05:37:34.282334 susetest apparmor.systemd[435]: Reloading AppArmor profiles Aug 05 05:37:34.283671 susetest systemd-remount-fs[448]: mount: /: mount point is busy. ... Aug 05 05:37:34.984770 susetest systemd[1]: Mounting /boot/writable... ... Aug 05 05:37:35.246908 susetest systemd[1]: Mounted /boot/writable. ... Aug 05 05:37:35.331954 susetest systemd[1]: Starting Remount Root and Kernel File Systems... ... Aug 05 05:37:35.500468 susetest systemd[1]: Finished Remount Root and Kernel File Systems. The first attempt to systemd-remount-fs.service fails because something has a file opened in RW mode, so it's attempted again later, when it's already too late. Not sure what to do about this. Make the ordering dependency more extreme by having boot-writable.mount Requires=systemd-mount-fs.service? -- You are receiving this mail because: You are the assignee for the bug.