The following was filed automatically by anaconda: anaconda 11.5.0.25 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devices.py", line 1507, in _addPV raise ValueError("pv is already part of this vg") File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 343, in createAllowedLvmPartitionsList self.vg._addPV(device) File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 997, in __init__ (self.lvmlist, sw) = self.createAllowedLvmPartitionsList(self.availlvmparts, self.storage.vgs) File "/usr/lib/anaconda/iw/partition_gui.py", line 1129, in editLVMVolumeGroup isNew) File "/usr/lib/anaconda/iw/partition_gui.py", line 1054, in editCB self.editLVMVolumeGroup(device) ValueError: pv is already part of this vg
Created attachment 334343 [details] Attached traceback automatically from anaconda.
At least it started up without having to wipe the previous installation. Selected custom layout and went to edit a previous partition/lv to assign mount point and options. probably a duplicate of a previous traceback. will try allowing it to start a fresh layout, there's no real stuff on the 1st drive and home is a second drive.
Created attachment 334435 [details] Attached traceback automatically from anaconda.
*** Bug 488987 has been marked as a duplicate of this bug. ***
*** Bug 489511 has been marked as a duplicate of this bug. ***
There's no traceback for me now, but editing a pre-existing LV has problems assigning the mount point (BZ 490301)
Now its failing again - 11.5.0.35 Almost any LVM layout besides the default fails either silently or with a "Filesystem not formatted"
So, the original traceback is no longer being seen? I wonder if that's because you are getting a new traceback before you'd get the old one, or if the old one has been fixed and is no longer getting hit. If you could attach the new traceback, that'd be helpful in determining which is the case. If the original bug report is no longer relevant, we should close out this report and open a new one for the new problem. Thanks.
the original traceback /seems/ to have been fixed in terms of the reported errors however, the symptoms are now being attributed to other exceptions. re-using an existing LV and trying too edit its properties still fails. Technically, I guess that *this* bug is fixed, when i next test tomorrow morning I'll be sure to file any tracebacks.