Activity log for bug #1801918

Date Who What changed Old value New value Message
2018-11-06 11:33:07 Jan Marquardt bug added bug
2018-11-06 13:26:09 Christian Ehrhardt  libvirt (Ubuntu): status New Confirmed
2018-11-06 13:38:01 Christian Ehrhardt  bug task added lvm2 (Ubuntu)
2018-11-06 13:39:33 Christian Ehrhardt  libvirt (Ubuntu): status Confirmed Invalid
2018-11-06 13:42:36 Christian Ehrhardt  description I am trying to create a logical volume storage pool with persistent device names for the block devices, because I can't/don't want to ensure that /dev/sd* names are persistent through reboots. virsh # pool-define-as web2067 logical - - /dev/disk/by-path/pci-0000:18:00.0-scsi-0:2:2:0 web2067 /dev/web2067 virsh # pool-build web2067 These two steps work as expected and the pv and the vg get created, but when I try to start the pool I get the following error: virsh # pool-start web2067 error: Failed to start pool web2067 error: unsupported configuration: cannot find any matching source devices for logical volume group 'web2067' If I do the same steps just with /dev/sdX instead of /dev/disk/by-path/..., the pool gets created correctly. According to the libvirt mailing list /dev and /dev/disk/by-path are supposed to work the same way. lvm2 tools do not store by-path values in their config. That can drive scripts/tools (like the libvirt case here) mad. Simplified example: $ sudo /sbin/pvcreate /dev/disk/by-path/virtio-pci-0000:00:07.0 $ sudo /sbin/pvs --noheadings -o pv_name,vg_name /dev/vdc It is NOT using /dev/disk/by-path/virtio-pci-0000:00:07.0 as instructed, but instead did the mapping to /dev/vdd and keeps that from now on. I know that "inside" lvm all that is done via metadata and it won't matter. But tools around it get confused. Not sure yet if it is a real issue, or just "works as designed". --- started as libvirt issue - keeping old desc below --- I am trying to create a logical volume storage pool with persistent device names for the block devices, because I can't/don't want to ensure that /dev/sd* names are persistent through reboots. virsh # pool-define-as web2067 logical - - /dev/disk/by-path/pci-0000:18:00.0-scsi-0:2:2:0 web2067 /dev/web2067 virsh # pool-build web2067 These two steps work as expected and the pv and the vg get created, but when I try to start the pool I get the following error: virsh # pool-start web2067 error: Failed to start pool web2067 error: unsupported configuration: cannot find any matching source devices for logical volume group 'web2067' If I do the same steps just with /dev/sdX instead of /dev/disk/by-path/..., the pool gets created correctly. According to the libvirt mailing list /dev and /dev/disk/by-path are supposed to work the same way.
2018-11-06 13:58:09 Christian Ehrhardt  libvirt (Ubuntu): status Invalid Incomplete
2018-11-06 13:58:12 Christian Ehrhardt  lvm2 (Ubuntu): status New Invalid
2018-11-06 14:48:37 Christian Ehrhardt  libvirt (Ubuntu): status Incomplete Invalid