Red Hat Bugzilla – Bug 864721
AttributeError: 'BTRFS' object has no attribute 'partitions'
Last modified: 2014-10-06 10:32:37 EDT
Description of problem:
selected a btrfs disk, tried guided partitioning, went back, enter again.
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.14 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 120, in populate
: for part in disk.format.partitions:
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 167, in refresh
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 665, in on_continue_clicked
:AttributeError: 'BTRFS' object has no attribute 'partitions'
Created attachment 624374 [details]
Created attachment 624375 [details]
Created attachment 624376 [details]
Created attachment 624377 [details]
Created attachment 624378 [details]
Created attachment 624379 [details]
Created attachment 624380 [details]
Created attachment 624381 [details]
Created attachment 624382 [details]
Created attachment 624383 [details]
Created attachment 624384 [details]
Created attachment 624385 [details]
Created attachment 624386 [details]
Created attachment 624387 [details]
Installer reported no space on virtual disk. I had just formated the partition before starting the VM in order to try to
recreate conditions of another test. Checked reclaim all space and the error occured as a result.
OS Release: Fedora release 18-Beta-TC2
Trying to work with 4 disks in VM. Each is a separate partition (originally formated at ext4,
not cleared). Apparently the installer thinks the drives are already partitioned and reports 0
bytes avaiable, but suggests to reclaim space. When that is selected, the error occurs.
OS Release: Fedora release 18-Beta-TC3
I have tried to use harddisk that has one partition with BTRFS filesystem. After selecting disk, this traceback showed.
OS Release: Fedora release 18-Beta-TC3
Attach your logs, people.
The original reporter has a btrfs filesystem on an unpartitioned disk. Both of the last two reporters claim to have hit this with partitioned disks but did not include logs.
I thought abrt attached the logs. Sorry. Have moved on however and logs no longer avail. Will try to recreate later.
dlehman has a fix for the original problem.
we've seen no report of this lately. did the fix for the 'original problem' get committed? can we close this?
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
Thank you for reporting this bug and we are sorry it could not be fixed.