Red Hat Bugzilla – Bug 139711
Traceback when removing LV with mounted filesystem.
Last modified: 2009-04-16 19:10:53 EDT
Description of problem:
Create an LV and make and mount a filesystem on it. Navigate to the
logical view of the LV and click "Remove Logical Volume". After
confirming that you're really really sure you want to do this and lose
your data the operation proceeds.
Got this traceback:
Traceback (most recent call last):
File "/usr/share/system-config-lvm/Volume_Tab_View.py", line 321, in
lv_data = self.model_factory.get_data_for_LV(lv_name)
File "/usr/share/system-config-lvm/lvm_model.py", line 665, in
words = lines.split(",")
IndexError: list index out of range
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This does not seem to be reproducible. I'll try to get a consistent
recipe and update here.
The key to making this happen is to have LVs of the same name in
For instance, create:
There are other more ubiquitous symptoms, which I just noticed. In
the left hand navitation tree if you open up to the logical view of
both VGs, the duplicate named LV is constantly highlighted.
This bug was a great catch. Now LVs in different VGs can have the same
names without bad things happening to the tree selection mechanism.
Fixed in 0.9.12-1.0
Verified in system-config-lvm-0.9.12-1.0.