Description of problem: I was testing bug 868671, i selected one unpartitioned disk still containing a btrfs volume member and set it to 'reformat' as '/' and 'finish partitioning'. Anaconda crashed at the MAIN HUB. Note: with 768mb ram the guest was unable to report the 'unknown error', with 2048 it could. The following was filed automatically by anaconda: anaconda 18.37.8 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1581, in check parts = self.stage1_disk.format.partedDisk.partitions File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1543, in sanityCheck if not self.bootloader.check(): File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 309, in checkStorage StorageChecker.warnings) = self.storage.sanityCheck() File "/usr/lib64/python2.7/threading.py", line 504, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run threading.Thread.run(self, *args, **kwargs) AttributeError: 'Ext4FS' object has no attribute 'partedDisk' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.6.10-4.fc18.x86_64 other involved packages: package: anaconda-18.37.8 product: Fedora release: Cannot get release name. type: libreport version: 18
Created attachment 671599 [details] File: anaconda-tb
Created attachment 671600 [details] File: anaconda.log
Created attachment 671601 [details] File: environ
Created attachment 671602 [details] File: ifcfg.log
Created attachment 671603 [details] File: packaging.log
Created attachment 671604 [details] File: program.log
Created attachment 671605 [details] File: storage.log
Created attachment 671606 [details] File: syslog
Really pushing things here. In F17 created raid 10 PV, used whole PV for VG and created LVs to use as /, /home and swap. Then in VM used /dev/md0 as VD. F18TC4 saw md0 as a single device but, as expected, said no space for installation. So, in partitioner, reused each LV as /, /home and swap. All ok so far, but I forgot that /boot has to be standard partition which the partitioner nicely informed me. Since I had an ide disk on the VM, I went back into the storage selection screen to select it for /boot. Upon clicking it the error occurred. I am sure I am trying things not remotely supported currently. Just say so and I'll close the bz if a new one is created. If this turns out to be a dup, then let me know if you want the logs which will be saved. (Note to self: 20130104-1) Package: anaconda-18.37.8 OS Release: Fedora release 18-TC4
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.