Description of problem: After creating thin LV, system-config-lvm aborts during startup. Version-Release number of selected component (if applicable): system-config-lvm.noarch 1.1.18-1.fc17 How reproducible: Steps to Reproduce: 1. create thin LV (see below) 2. launch system-config-lvm Details: system-config-lvm # works fine lvcreate -L 100G -T g2/pool lvcreate -T g2/pool -V 80G --name vimages system-config-lvm # fails with stacktrace $ system-config-lvm BDB2053 Freeing read locks for locker 0xeb: 1923/140575145375744 BDB2053 Freeing read locks for locker 0xec: 1923/140575145375744 BDB2053 Freeing read locks for locker 0xed: 1923/140575145375744 BDB2053 Freeing read locks for locker 0xee: 1923/140575145375744 Traceback (most recent call last): File "/usr/share/system-config-lvm/system-config-lvm.py", line 172, in <module> runFullGUI() File "/usr/share/system-config-lvm/system-config-lvm.py", line 157, in runFullGUI blvm = baselvm(glade_xml, app) File "/usr/share/system-config-lvm/system-config-lvm.py", line 105, in __init__ self.volume_tab_view = Volume_Tab_View(glade_xml, self.lvmm, self.main_win) File "/usr/share/system-config-lvm/Volume_Tab_View.py", line 136, in __init__ self.prepare_tree() File "/usr/share/system-config-lvm/Volume_Tab_View.py", line 225, in prepare_tree self.model_factory.reload() File "/usr/share/system-config-lvm/lvm_model.py", line 168, in reload self.__query_LVs() File "/usr/share/system-config-lvm/lvm_model.py", line 526, in __query_LVs extent_block = ExtentBlock(pv, lv, ph_ext_beg, seg_size) File "/usr/share/system-config-lvm/ExtentBlock.py", line 14, in __init__ self.__pv.add_extent_block(self) AttributeError: 'NoneType' object has no attribute 'add_extent_block'
Thin pools/volumes are not supported because this project is in maintaince mode only but it surely should not crash. Patch that fixes this was sent to upstream and will be part of next version. http://git.fedorahosted.org/cgit/system-config-lvm.git/commit/?id=97b353cc0469f6067f53117a9557d6750bd00dc2
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.