Created attachment 987798 [details] rdsoreport of the instalation. Description of problem: Python-blivet crashes with lvm-cache partitioned scheme (already done, see below) (probably on devicetree.py) Version-Release number of selected component (if applicable): Fedora 21 How reproducible: Try to create a lvm-cache partitioning scheme crashes the blivet python. Steps to Reproduce: 1.Before instalation, create a lvm-cache partitioning 2.Start anaconda 3.On select the partitions, anaconda (python-blivet) crashes. Actual results: Crash Expected results: Install on a lvm-cache create scheme. Additional info: Actual LVM scheme: #lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lv_cache_home vg_system Cwi---C--- 40.00g lv_cache_root vg_system Cwi---C--- 1.00g lv_home vg_system Cwi-a-C--- 750.00g lv_cache_home [lv_home_corig] lv_root vg_system Cwi-a-C--- 40.00g lv_cache_root [lv_root_corig] lv_tmp vg_system -wi-a----- 10.00g lv_varlog vg_system -wi-a----- 10.00g # vgs VG #PV #LV #SN Attr VSize VFree vg_system 2 7 0 wz--n- 897.39g 38.39g #pvs PV VG Fmt Attr PSize PFree /dev/sda3 vg_system lvm2 a-- 47.39g 5.39g # ssd disk /dev/sdg1 vg_system lvm2 a-- 850.00g 33.00g # raid-1 hdd disks #lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 55.9G 0 disk ├─sda1 8:1 0 512M 0 part ├─sda2 8:2 0 4G 0 part └─sda3 8:3 0 51.4G 0 part ├─vg_system-lv_cache_root_cdata 253:3 0 1G 0 lvm │ └─vg_system-lv_root 253:6 0 40G 0 lvm ├─vg_system-lv_cache_root_cmeta 253:4 0 10G 0 lvm │ └─vg_system-lv_root 253:6 0 40G 0 lvm ├─vg_system-lv_cache_cdata 253:9 0 40G 0 lvm │ └─vg_system-lv_home 253:12 0 750G 0 lvm └─vg_system-lv_cache_cmeta 253:10 0 1G 0 lvm └─vg_system-lv_home 253:12 0 750G 0 lvm sdg 8:96 0 931.3G 0 disk └─sdg1 8:97 0 850G 0 part ├─vg_system-lv_root_corig 253:5 0 40G 0 lvm │ └─vg_system-lv_root 253:6 0 40G 0 lvm ├─vg_system-lv_tmp 253:7 0 10G 0 lvm ├─vg_system-lv_varlog 253:8 0 10G 0 lvm └─vg_system-lv_home_corig 253:11 0 750G 0 lvm └─vg_system-lv_home 253:12 0 750G 0 lvm sdh 8:112 1 251.9M 0 disk └─sdh1 8:113 1 251M 0 part /mnt sr0 11:0 1 1.4G 0 rom /run/initramfs/live loop0 7:0 0 12K 1 loop loop1 7:1 0 1.8M 1 loop └─live-osimg-min 253:2 0 6G 1 dm loop2 7:2 0 1.3G 1 loop loop3 7:3 0 6G 1 loop ├─live-rw 253:0 0 6G 0 dm / ├─live-base 253:1 0 6G 1 dm └─live-osimg-min 253:2 0 6G 1 dm loop4 7:4 0 512M 0 loop └─live-rw 253:0 0 6G 0 dm / # commands list in order (lvm partitioning creation - to reproduce) pvcreate /dev/sdg1 vgcreate vg_system /dev/sdg1 lvcreate -L 730G -n lv_home vg_system vgextend vg_system /dev/sda3 lvcreate -L 1G -n lv_cache_meta_home vg_system /dev/sda3 lvcreate -L 1G -n lv_cache_meta_root vg_system /dev/sda3 lvcreate -L 25G -n lv_cache_home vg_system /dev/sda3 lvcreate -L 15G -n lv_cache_root vg_system /dev/sda3 lvcreate -L 16G -n lv_slow_swap vg_system /dev/sdg1 lvcreate -L 50G -n lv_root vg_system /dev/sdg1 lvcreate -L 10G -n lv_tmp vg_system /dev/sdg1 lvcreate -L 10G -n lv_varlog vg_system /dev/sdg1 lvconvert --type cache-pool --poolmetadata vg_system/lv_cache_meta_root vg_system/lv_cache_root lvconvert --type cache-pool --poolmetadata vg_system/lv_cache_meta_home vg_system/lv_cache_home lvconvert --type cache --cachepool vg_system/lv_cache_root vg_system/lv_root lvconvert --type cache --cachepool vg_system/lv_cache_home vg_system/lv_home
Anyone who whants to reproduce it, can skip the home cache, and do only root cache. any VM is possible to reproduce with to disks allocated.
Thanks for the report! If you still have the installed system, the log files will be in /var/log/anaconda - it'd be very useful if you can attach those.
I've experienced this too on my own workstation that uses LVM cache. It can be easily reproduced outside of anaconda just in a python shell as: >>> import blivet >>> b = blivet.Blivet() >>> b.reset() traceback...
(In reply to awilliam from comment #2) > Thanks for the report! If you still have the installed system, the log files > will be in /var/log/anaconda - it'd be very useful if you can attach those. Don't have it anymore. but it's easy to reproduce it.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This should be resolved in both F22 and Rawhide versions of python-blivet.