Hello bugproxy, or anyone else affected, Accepted lvm2 into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu3.18.10.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lvm2 (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed-cosmic -- 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/1830169 Title: lvm udev rule fails to call systemd-run Status in Ubuntu on IBM z Systems: In Progress Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Xenial: New Status in lvm2 source package in Bionic: New Status in lvm2 source package in Cosmic: Fix Committed Status in lvm2 source package in Disco: Fix Committed Status in lvm2 source package in Eoan: Fix Released Bug description: [Impact] Judging from the rule, this probably means that volumes do not disappear when the physical volume disappears. [Test case] Not available. But since it's just a path fix, it should not be a problem. [Regression potential] Removal might now actually work correctly, but it's not entirely clear how that could cause a regression. [Other info] In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run command during removal ------- ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm pvscan --cache $major:$minor", GOTO="lvm_end" But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin /systemd-run. xxxxxxxxxx:~$ cat /etc/issue Ubuntu 18.04.2 LTS \n \l xxxxxxxxxx:~$ ls /bin/systemd-run ls: cannot access '/bin/systemd-run': No such file or directory xxxxxxxxxx:~$ ls /usr/bin/systemd-run /usr/bin/systemd-run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
