Description of problem: I have a machine with one VG, one LV and one MD RAID and blivet doesn't show any LVs and MD arrays. sdb 8:16 0 1G 0 disk ├─sdb1 8:17 0 94M 0 part │ └─vg-lv (dm-0) 253:0 0 40M 0 lvm ├─sdb2 8:18 0 95M 0 part ├─sdb3 8:19 0 94M 0 part ├─sdb4 8:20 0 94M 0 part │ └─md127 9:127 0 281.5M 0 raid0 ├─sdb5 8:21 0 95M 0 part │ └─md127 9:127 0 281.5M 0 raid0 ├─sdb6 8:22 0 94M 0 part │ └─md127 9:127 0 281.5M 0 raid0 Version-Release number of selected component (if applicable): python-blivet-0.6-1.fc19.noarch How reproducible: always Steps to Reproduce: 1. init blivet and do devicetree.populate 2. print blivet.lvs, blivet.mdarrays 3. Actual results: blivet.lvs and blivet.mdarrays are empty Expected results: blivet.lvs and blivet.mdarrays contains LVs and arrays dlehman has a patch for MD RAIDs, not sure about LVs.
A minimal reproducer python script would be helpful.
Created attachment 702655 [details] reproducer There is not much to see in the reproducer, just devicetree.populate() and print. The storage setup is just simple raid0 and one lv: mdadm -C -l 0 -n 3 /dev/md/0_0 /dev/sdb{4,5,6} vgcreate vg /dev/sdb{1,2} lvcreate -n lv -l 10 /dev/vg
Created attachment 702657 [details] blivet 0.7 log I noticed python-blivet-0.7-1.fc19.noarch in today's rawhide, here is log of the reproducer.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Seems to be working in python-blivet-0.10