Description of problem: on guest BTRF-3 i did: 1. selected the first big disks and two small disks (400mb) each. 2. went to manual partitioning (set type to btfs), deleted all partitions. 3. created a /boot, swap and / on the fist disk (by using the 'tool' icon, making sure that these were not on the small disks) 4. the i tried to create 1.6gb /home on the small disks but anaconda created it as 7gb, so i changed the size manually and then anaconda crasshed on apply 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/storage/devices.py", line 4006, in path return self.parents[0].path File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2615, in <lambda> return sorted(self.devicetree.devices, key=lambda d: d.path) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2615, in devices return sorted(self.devicetree.devices, key=lambda d: d.path) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2620, in mountpoints for device in self.devices: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1737, in mountpoints return self.fsset.mountpoints File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1712, in bootDevice dev = self.mountpoints.get("/boot", self.rootDevice) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/partitioning.py", line 756, in doPartitioning storage.bootDevice.req_bootable = True File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2005, in allocatePartitions doPartitioning(self) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1993, in setContainerMembers self.allocatePartitions() File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2167, in newDevice members=members, device=device) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1193, in _save_right_side raid_level=raid_level) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2481, in on_apply_clicked self._save_right_side(self._current_selector) IndexError: list index out of range 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 671647 [details] File: anaconda.log
Created attachment 671648 [details] File: environ
Created attachment 671649 [details] File: ifcfg.log
Created attachment 671650 [details] File: packaging.log
Created attachment 671651 [details] File: program.log
Created attachment 671652 [details] File: storage.log
Created attachment 671653 [details] File: syslog
Created attachment 671654 [details] File: anaconda-tb
i did manual partitioning, erased all parititions. on the first big disks, i created a btrfs filesystem with several subvolumes /,/boot, /home and swpa (as a standard partition) then i tried to create another btrfs filesystem for /app with the other small 400mb disks. The only thing i could do was to create it as another subvol, change on which disks it should be (excluded de big disk) and then i had to change it size to match the free space but it crashed. Package: anaconda-18.37.10 OS Release: Fedora release 18
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.