** Changed in: lvm2 (Fedora)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped
Hi Yuri,
there was no recent change in regard to lvm handling in libvirt or lvm itself
that would obviously be related. Which Ubuntu release are you on - and between
which package versions did you upgrade?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
This seems like a new problem to my after 6/24/20 update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1701234.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
It seems - somewhat expected - that the solution needs to be a bit
bigger due to further service dependencies that might create a loop.
Until that solution is sorted out upstream we should not implement
another custom emergency fix that might cause more trouble.
Instead while we wait on the final
Linked the related RH bug that was mentioned upstream
https://bugzilla.redhat.com/show_bug.cgi?id=1701234
** Bug watch added: Red Hat Bugzilla #1701234
https://bugzilla.redhat.com/show_bug.cgi?id=1701234
** Also affects: lvm2 (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1701234
** Changed in: lvm2
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832859
Title:
during shutdown libvirt-guests gets stopped after file system
Reported: https://github.com/lvmteam/lvm2/issues/18
Suggested: https://github.com/lvmteam/lvm2/pull/19
** Bug watch added: github.com/lvmteam/lvm2/issues #18
https://github.com/lvmteam/lvm2/issues/18
** Also affects: lvm2 via
https://github.com/lvmteam/lvm2/issues/18
Importance: Unknown
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
I can confirm that adding Before=local-fs.target to blk-
availability.service solved the issue for me. Now everything happens in
the correct order. I attached the shutdown journal for reference.
** Attachment added: "shutdown.txt"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1832859/
yeah I think I found the issue in your log.
Consider [1] again and look at
/lib/systemd/system/blk-availability.service
This is what calls blkdeactivate on shutdown.
It only has a
WantedBy=sysinit.target
But no ordering Before anything.
It even has
DefaultDependencies=no
which will make it
11 matches
Mail list logo
