Red Hat Bugzilla – Bug 485622
Partitioning traceback with new pyparted - KeyError: 's'
Last modified: 2009-02-20 18:15:55 EST
Created attachment 331967 [details]
Exception report for anaconda 220.127.116.11
Description of problem:
After booting from boot.iso as of 2009-02-15, an exception occurs when an existing existing logical volume is double clicked for further editing. 'Bug buddy' appears on the screen and displays a traceback which is attached to this report.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot "boot.iso" from USB stick.
2. Choose custom layout in order to reuse an existing VG.
3. Click the first LV in the volume window.
Anaconda throws an exception.
Volume gets opened for setting the mount point etc.
- The exception happens for earlier version of anaconda including the
F11-Alpha boot image.
- F10 was not affected by this bug.
Created attachment 332042 [details]
Exception report for anaconda 18.104.22.168-1 on x86 (Intel PR440FX)
Just happens here as on a Tyan Tomcat K8E running the x86_64 bit version. No problem when running the partitioner from the F11 Alpha i686 live CD. Of course, the corresponding boot.iso mentioned in the initial report could not work as stage2.img was still downloaded from the current rawhide tree. Maybe a problem with pyparted-2.0.0-1?
*** Bug 485943 has been marked as a duplicate of this bug. ***
*** Bug 485987 has been marked as a duplicate of this bug. ***
No improvement for "rawhide" as of 2009-02-18:
Yep, that's why this bug is still in NEW.
*** Bug 486058 has been marked as a duplicate of this bug. ***
*** Bug 486123 has been marked as a duplicate of this bug. ***
*** Bug 486220 has been marked as a duplicate of this bug. ***
Created attachment 332645 [details]
Patch to fix the issue. Under review now.
Created attachment 332771 [details]
Fixed in anaconda-22.214.171.124-1