http://bugzilla.suse.com/show_bug.cgi?id=1156086 http://bugzilla.suse.com/show_bug.cgi?id=1156086#c7 José Iván López González <jlopez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |jlopez@suse.com Resolution|--- |DUPLICATE --- Comment #7 from José Iván López González <jlopez@suse.com> --- The scenario recognized by YaST simply does not make sense (see screenshot). There are two LVM PVs, and both are associated to the same two underlying devices (/dev/sda and /dev/md/HDD)! A LVM PV can only be over a single device. I would say this nonsense scenario was produced because the issue with lvm2 package shipped in openSUSE 15.1 [1]. But the lvm2 package was already fixed [2], so the problem is gone with an updated Leap 15.1 or Tumbleweed.

From the YaST point of view, there is nothing to fix. The nil:NilClass exception occurs because there is an LVM PV without an associated block device and that PV belongs to none LVM VG. I would say that insane scenario only would be possible with broken lvm tools.

Closing the bug as duplicated. [1] https://bugzilla.suse.com/show_bug.cgi?id=1136641 [2] https://build.opensuse.org/request/show/743388 *** This bug has been marked as a duplicate of bug 1136641 *** -- You are receiving this mail because: You are on the CC list for the bug.