Red Hat Bugzilla – Bug 864842
AttributeError: 'NoneType' object has no attribute 'id'
Last modified: 2012-11-26 09:13:32 EST
Description of problem:
In the partitioning dialog I clicked on "summary" (or similar), selected my disk and hit Remove. I assumed that would erase the whole disk.
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
:The following was filed automatically by anaconda:
:anaconda 18.14 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/cart.py", line 136, in on_remove_clicked
: if disk.id == self._store[itr][ID_COL]:
:AttributeError: 'NoneType' object has no attribute 'id'
Created attachment 624665 [details]
Created attachment 624666 [details]
Created attachment 624667 [details]
Created attachment 624668 [details]
Created attachment 624669 [details]
Created attachment 624670 [details]
Created attachment 624671 [details]
Created attachment 624672 [details]
Created attachment 624673 [details]
Created attachment 624674 [details]
Created attachment 624675 [details]
Created attachment 624676 [details]
Created attachment 624677 [details]
Always reproducible. Proposing as Beta blocker.
No, it won't erase the whole disk. It just removes it from consideration as an installation source, same as if you unclicked it on the storage overview screen. Still shouldn't crash.
(In reply to comment #15)
> No, it won't erase the whole disk. It just removes it from consideration as
> an installation source, same as if you unclicked it on the storage overview
That's not clear at all. Of course that's a different issue, let's fix crashes first.
I wouldn't say it's not clear. The wording is "Remove", not "Erase" or "Delete Filesystems" or anything like that. Also when you click it, you can later see the effects on the storage overview.
anaconda-18.15-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.15-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Created attachment 625591 [details]
Discussed at 2012-10-11 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-11/f18beta-blocker-review-3.1.2012-10-11-16.04.log.txt . Agreed that this is not a Beta blocker, it doesn't really hit any criteria, the operation you have to do to hit it is not a valid one (so it's not stopping you doing anything you'd actually want to do), and it's easy to recover, just reboot and start over (you're likely to hit this early in your install attempt so you won't have lost a lot of work).
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.
Confirmed fixed in anaconda 18.29.2.
Removing CommonBugs because this has been fixed before F18 Beta release.