Red Hat Bugzilla – Bug 863451
AttributeError: 'DeviceFormat' object has no attribute 'peStart'
Last modified: 2012-10-24 19:14:32 EDT
Description of problem:
* deleted all existing partions
* used the feature to create a partition template (or whatever such feature is called -some people call it "automatic partitioning prima or bis"-)
tried to remove devices in the UNKNOWN tree....
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda
:The following was filed automatically by anaconda:
:anaconda 18.12 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 2273, in size
: size += max(0, self.align(pv.size - pv.format.peStart))
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 680, in _do_refresh
: selector = page.addDevice(u.format.name, Size(spec="%f MB" % u.size), None, self.on_selector_clicked)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1507, in on_remove_clicked
:AttributeError: 'DeviceFormat' object has no attribute 'peStart'
Created attachment 622221 [details]
Created attachment 622222 [details]
Created attachment 622223 [details]
Created attachment 622224 [details]
Created attachment 622225 [details]
Created attachment 622226 [details]
Created attachment 622227 [details]
Created attachment 622228 [details]
Created attachment 622229 [details]
Created attachment 622230 [details]
Created attachment 622231 [details]
Created attachment 622232 [details]
Created attachment 622233 [details]
Created attachment 622234 [details]
the issue happens when deleting the last entry in the 'UNKNOWN' (when the whole tree ?should? disappear)
By just starting to delete the entries in 'UNKNOWN' tree, it happens after
deleting the last entry.
Note: the elements are not really deleted, but just assume they are and continue one by one until the last one.
I propose it as a blocker because maybe that is the disc in which one might want to install fedora (and thus, it cannot generate the requiered free space)
Discussed at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt .
As we understand it, this bug can be described as follows:
It affects the custom partitioning mode. The design of custom partitioning is that existing partitions are grouped by the OS installation they appear to be a part of. Partitions that cannot be associated with an existing OS installation are grouped together into an 'UNKNOWN' group. This crash is triggered by deleting the last partition in the 'UNKNOWN' group.
Assuming that description is accurate, we accept this bug as a blocker per Beta criterion "The installer's custom partitioning mode must be capable of the following: Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types" . This decision can be re-visited if the description above turns out to be incorrect. We will test to verify the bug is as described.
Discussed at 2012-10-17 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-17/f18beta-blocker-review-4.2012-10-17-16.00.log.txt . Anaconda team, can you please look into this? It doesn't appear to have received any attention.
This still doesn't seem to have received any attention.
Reartes, can you reproduce this with 18.19 (TC6)? It'd be useful to know if it's still a problem.
I tried with several guests (F18b TC6) and i was unable to reproduce it.
I managed to delete all unknown partitions (and the known ones) without crashing.
As no-one else has hit this, I think possibly our best course is to close it for now; if anyone hits it, we can re-open it. Assuming it's been fixed by the many changes to the partitioning code between 18.12 and 18.19, setting CLOSED ERRATA.