Bug 626220 - AttributeError: VolumeGroupEditor instance has no attribute 'volnameEntry'
Summary: AttributeError: VolumeGroupEditor instance has no attribute 'volnameEntry'
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:683b119161ad933b7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-22 19:50 UTC by Geert Jansen
Modified: 2013-03-13 06:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-24 19:49:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (354.99 KB, text/plain)
2010-08-22 19:50 UTC, Geert Jansen
no flags Details
Traceback as requested (365.97 KB, text/plain)
2010-08-23 07:39 UTC, Geert Jansen
no flags Details

Description Geert Jansen 2010-08-22 19:50:21 UTC
The following was filed automatically by anaconda:
anaconda 14.15 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/lvm_dialog_gui.py", line 1018, in convertToActions
    volname = self.volnameEntry.get_text().strip()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1776, in editLVMLogicalVolume
    actions = vgeditor.convertToActions()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1638, in editCB
    self.editLVMLogicalVolume(lv = device)
AttributeError: VolumeGroupEditor instance has no attribute 'volnameEntry'

Comment 1 Geert Jansen 2010-08-22 19:50:28 UTC
Created an attachment (id=440253)
Attached traceback automatically from anaconda.

Comment 2 Chris Lumens 2010-08-22 23:15:48 UTC
Looks like exception reporting has somehow broken - something must be going wrong with either report or python-bugzilla.  Can you please attach /tmp/anaconda-tb-* to this report?

Comment 3 Geert Jansen 2010-08-23 07:39:05 UTC
Created attachment 440310 [details]
Traceback as requested

Comment 4 Chris Lumens 2010-08-23 14:25:13 UTC
Looking at the code, I don't see how that situation is possible.  Did you do something where you went back and forth between UI elements, possibly causing a dialog to come and go during partitioning setup?

Comment 5 Geert Jansen 2010-08-23 15:16:35 UTC
Not sure what you would be back and forth. My usage of the GUI was pretty basic. The system is already partitioned and a few partitions needed to be preserved. I used "custom layout" when selecting how to partition. Then i click on an LV, configure the mount point, and hit OK. At that point i get the exception.

I got the same problem in F13 too.

Comment 6 Chris Lumens 2010-08-24 19:49:19 UTC
We are completely unable to reproduce this error in testing, and I've never heard any other reports along these lines.  Something weird is going on, but I don't know what.

Comment 7 Geert Jansen 2010-08-25 07:17:22 UTC
Obviously there's a bug though. I was able to get it to bomb out consistently. I'll try again on my new install, see if it bombs out there as well.


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