Description of problem: enter storage and selected some disks which contained btrfs partitions Version-Release number of selected component: anaconda-18.14 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :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/resize.py", line 123, in populate : if dev.isExtended and disk.format.logicalPartitions: : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 167, in refresh : self.populate(disks) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 665, in on_continue_clicked : resizeDialog.refresh(disks) :AttributeError: 'BTRFSVolumeDevice' object has no attribute 'isExtended'
Created attachment 624357 [details] File: anaconda-tb
Created attachment 624358 [details] File: product
Created attachment 624359 [details] File: type
Created attachment 624360 [details] File: ifcfg.log
Created attachment 624361 [details] File: storage.log
Created attachment 624362 [details] File: version
Created attachment 624363 [details] File: environ
Created attachment 624364 [details] File: anaconda.log
Created attachment 624365 [details] File: syslog
Created attachment 624366 [details] File: hashmarkername
Created attachment 624367 [details] File: packaging.log
Created attachment 624368 [details] File: cmdline_file
Created attachment 624369 [details] File: release
Created attachment 624370 [details] File: program.log
*** This bug has been marked as a duplicate of bug 864180 ***
This will be fixed in anaconda-18.17-1.
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18
Package anaconda-18.17-1.fc18: * 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.17-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18 then log in and leave karma (feedback).
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18
Package anaconda-18.18-1.fc18: * 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.18-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18 then log in and leave karma (feedback).
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18
this should not happen. anaconda was behaving incorreclty (RHBZ: 868671) when i hit this again. Package: anaconda-18.19 OS Release: Fedora release 18-Beta-TC6
selected the four remaining "0 byte disks" and tried to reach the reclaim space dialog Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7
Created attachment 637538 [details] anaconda.log
Created attachment 637539 [details] anaconda tb
Created attachment 637540 [details] program.log
Created attachment 637542 [details] storage.log
Created attachment 637543 [details] disk vdb partition iformation
Created attachment 637544 [details] disk vdc, vdd, vde, vdf partition iformation
Created attachment 637545 [details] blkid While unpartitioned, BTRFS filesystem(s) can still be detected. I do not remember of vdb was part of it or not. So there are unpartitioned devices with a PSEUDO-WHOLE DISKS FILESYSTEM (pseudo whole, in the sense that the WHOLE spans multiple disks). Can this be the cause of these '0 byte disks' ?
setting back to ASSIGNED, as reartes appears to have this in a build after it was 'fixed'.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.