Bug 490155 - Exception when editing a logical volume
Exception when editing a logical volume
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
anaconda_trace_hash:383f2212e4238a3e9...
:
Depends On:
Blocks: F11Beta/F11BetaBlocker
  Show dependency treegraph
 
Reported: 2009-03-13 11:47 EDT by Tomas Mraz
Modified: 2009-03-15 11:00 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-03-15 11:00:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (78.84 KB, text/plain)
2009-03-13 11:47 EDT, Tomas Mraz
no flags Details

  None (edit)
Description Tomas Mraz 2009-03-13 11:47:36 EDT
The following was filed automatically by anaconda:
anaconda 11.5.0.28 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/devices.py", line 1199, in _setName
    raise DeviceError("device is active")
  File "/usr/lib/anaconda/storage/devices.py", line 1205, in <lambda>
    lambda d,n: d._setName(n))
  File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 911, in run
    self.vg.name = volname
  File "/usr/lib/anaconda/iw/partition_gui.py", line 1140, in editLVMVolumeGroup
    actions = vgeditor.run()
  File "/usr/lib/anaconda/iw/partition_gui.py", line 1064, in editCB
    self.editLVMVolumeGroup(device)
DeviceError: device is active
Comment 1 Tomas Mraz 2009-03-13 11:47:44 EDT
Created attachment 335107 [details]
Attached traceback automatically from anaconda.
Comment 2 Tomas Mraz 2009-03-13 12:05:20 EDT
Similar to bug 489022 but the exception is different.
Comment 3 Tomas Mraz 2009-03-15 11:00:06 EDT
It seems that with the current image this crash is gone. Unfortunately the image is still uninstallable.

Note You need to log in before you can comment on or make changes to this bug.