abrt version: 2.0.5
reason: AttributeError: 'NoneType' object has no attribute 'path'
time: Sat Sep 10 22:54:39 2011
:The following was filed automatically by anaconda:
:anaconda 16.14.6 exception report
:Traceback (most recent call first):
: File "/tmp/updates/pyanaconda/storage/__init__.py", line 2252, in mkDevRoot
: dev = "%s/%s" % (instPath, root.path)
: File "/tmp/updates/pyanaconda/storage/__init__.py", line 1314, in mkDevRoot
: File "/tmp/updates/pyanaconda/upgrade.py", line 241, in upgradeMountFilesystems
: File "/tmp/updates/pyanaconda/dispatch.py", line 360, in dispatch
: self.dir = self.steps[self.step].target(self.anaconda)
: File "/tmp/updates/pyanaconda/gui.py", line 88, in return_false
: func(*args, **kwargs)
:AttributeError: 'NoneType' object has no attribute 'path'
I would like to point out that this happened after using the update image from Ales Kozumplik, mentioned here: https://bugzilla.redhat.com/show_bug.cgi?id=728188#c10 (I hit the error mentioned in that bug)
Also, my filesystem setup is a multidevice btrfs setup with a real "root" F15 filesystem living in a btrfs subvolume.
(In reply to comment #1)
> I would like to point out that this happened after using the update image from
> Ales Kozumplik, mentioned here:
> https://bugzilla.redhat.com/show_bug.cgi?id=728188#c10 (I hit the error
> mentioned in that bug)
That image is one month old (containing all the old files). Please retest in the latest F16.
Sadly I can't fully test it, because anaconda still doesn't support btrfs subvolumes. But until the partition selection phase I didn't have failures, so I guess it has been fixed...
I must reopen this bug: I just tried preupgrade with the new F16 Beta and I had an error. When I tried to report it the bug reporter said me that it was a duplicate of this bug...
Please attach the traceback you are getting - that'd be the /tmp/anaconda-tb-* file. Thanks.
I just filed a new bug that I got after trying the install DVD instead of using preupgrade...and I just realized that the python traceback seems similar and it may be the same bug. Since that bug already has attached the anaconda traceback, maybe this bug should be closed?
(the new bug is #743647)
*** This bug has been marked as a duplicate of bug 743647 ***