** Description changed:

- 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"
+ [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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830169

Title:
  lvm udev rule fails to call systemd-run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to