Red Hat Bugzilla – Bug 499662
anaconda -50 traceback: attribute error
Last modified: 2009-08-04 15:36:42 EDT
The following was filed automatically by anaconda:
anaconda 18.104.22.168 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/iw/partition_gui.py", line 183, in __init__
self.partedPartition = partition.partedPartition
File "/usr/lib/anaconda/iw/partition_gui.py", line 258, in add
stripe = DiskStripeSlice(self, partition, self.tree, self.editCB)
File "/usr/lib/anaconda/iw/partition_gui.py", line 819, in populate
File "/usr/lib/anaconda/iw/partition_gui.py", line 1338, in getScreen
self.populate(initial = 1)
File "/usr/lib/anaconda/gui.py", line 1423, in setScreen
new_screen = self.currentWindow.getScreen(anaconda)
File "/usr/lib/anaconda/gui.py", line 1340, in nextClicked
AttributeError: 'NoneType' object has no attribute 'partedPartition'
Created attachment 342856 [details]
Attached traceback automatically from anaconda.
http://etc install from redhat.com.
After detecting storage devices, including encrypted LVs, got traceback after clicking custom partitioning.
*** Bug 499714 has been marked as a duplicate of this bug. ***
This should be fixed in the next build of anaconda.
Couldn't test due to bz 499854.
Per discussion on irc://irc.freenode.net/#anaconda ... adding to F11AnacondaBlocker
I will attempt to retest using the following reproducer noted in bug#499714
= Steps to reproduce =
* Install autopart
* Initiate a new install, and select 'Custom partition'
* resize previous '/' logical volume to 5000
* add a new '/' using remaining free space in volume group
* resize previous '/boot' partition from 196 to 195
with anaconda .52, got into the custom partitioning which is good, but then hit 499828 which may not be related. Will try again without trying to mount any luks LVs.
Not using the comment 7 method and not mounting any luks LVs, installed OK.
Retesting this bug using the procedure in comment#7, I ran into bug#500991
While re-editing the previous '/' logical volume during the produced in comment#7, I also ran into bug#500995
Retesting the exact procedure in comment#7 this time does *not* result in the reported failure.
I do however hit bug#501000 while attempting to activate the partitions.
Created attachment 344192 [details]
FSError: filesystem has not been created
Following the above test case, when I tried to activate I got the attached traceback--seems to be a new bug? If so I can create a new bz, auto bz after the traceback would not work since it insists on looking for storage devices when those routines may have been clobbered--bz 497240.
I did not do the install autopart step since I don't know how to do that and assumed (correctly, I hope) that it is part of anaconda.
Forgot to add I inspected both / and /boot after the failure and they were not touched during the attempt.
Clyde: looks like you and I both hit bug#500991
Unable to retest, blocked by bug#501000. The reproducer is posted in this and the other bug (https://bugzilla.redhat.com/show_bug.cgi?id=501000#c6).
Retested using anaconda-22.214.171.124 (F-11-RC4) and no longer seeing this failure. Closing this bug.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here: