Thanks Erlend for the log.
I'm glad that the suggestion worked - now we need to check in which scope the
file is defined and ask for a change there - this should also ensure we are not
missing any hidden requirement that would be thwarted by that change (I could
think of it starting too late for other things then, or even to create a
dependency loop as it has quite some After dependencies).
The file is installed since late 2017
196 lvm2 (2.02.173-2) unstable; urgency=medium
...
200 * Install and enable blk-availability service.
Its actual content is from upstream, so this is the place to discuss it.
scripts/blk_availability_systemd_red_hat.service.in
I have found that newer versions have added one dependency.
=> https://github.com/lvmteam/lvm2/issues/17
But that only ensures it doesn't reach shutdown.target before this is done.
It does -not- ensure devices aren't unmounted before the FS on them is finished.
** Bug watch added: github.com/lvmteam/lvm2/issues #17
https://github.com/lvmteam/lvm2/issues/17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file system unmount
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs