Bug 579025 - KeyError: 'lvexp1'
Summary: KeyError: 'lvexp1'
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-02 07:40 UTC by Ales Kozumplik
Modified: 2014-09-30 23:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-07 13:08:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 606628 0 medium CLOSED anaconda crash when renaming new logical volume 2021-02-22 00:41:40 UTC

Internal Links: 606628

Description Ales Kozumplik 2010-04-02 07:40:13 UTC 
The following was filed automatically by anaconda:
anaconda 13.37 exception report
Traceback (most recent call first):
  File "/tmp/updates/iw/lvm_dialog_gui.py", line 913, in updateLogVolStore
    format = self.luks[lv['name']]
  File "/tmp/updates/iw/lvm_dialog_gui.py", line 797, in editLogicalVolume
    self.updateLogVolStore()
  File "/tmp/updates/iw/lvm_dialog_gui.py", line 810, in editCurrentLogicalVolume
    self.editLogicalVolume(lv)
  File "/tmp/updates/iw/lvm_dialog_gui.py", line 850, in editLogicalVolumeCB
    self.editCurrentLogicalVolume()
KeyError: 'lvexp1'
Comment 1 Chris Lumens 2010-04-05 14:01:06 UTC 
Do you have the whole traceback as well?  I don't know why it didn't get saved to this bug.
Comment 2 Ales Kozumplik 2010-04-06 06:24:58 UTC 
No. The machine didn't seem to do anything 2 minutes after starting the report so I rebooted it. Maybe bugzilla was being slow and stupid again, I need to give it more time the next time.
Comment 3 Chris Lumens 2010-04-06 13:09:43 UTC 
Putting back into needinfo until you can get the full traceback.  If you can't, I guess we'll have to close it.
Comment 4 Ales Kozumplik 2010-04-07 08:47:18 UTC 
Dammit, I can't reproduce this. It happened once when I was working on the bug 577824 but now I can't trigger it with that image. I think we can close this and, if it's meant to happen, it will resurface again.
Comment 5 Chris Lumens 2010-04-07 13:08:10 UTC 
Yeah, that's pretty frustrating.
Note You need to log in before you can comment on or make changes to this bug.