@hws as the status says on launchpad, both xenial and bionic are "in progress". Awaiting SRU team reviews to be accepted into -proposed.
-- 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: Fix Committed Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Xenial: In Progress Status in lvm2 source package in Bionic: In Progress Status in lvm2 source package in Cosmic: Fix Released Status in lvm2 source package in Disco: Fix Released 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
