Description of problem: Create 5GB disc image. Create 500MB '/boot' Attempt to create '/' from the remaining space. Version-Release number of selected component: anaconda-18.24-1.fc18.x86_64 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 kernel: 3.6.5-2.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.24 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 374, in _removeDevice : raise ValueError("Cannot remove non-leaf device '%s'" % dev.name) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 424, in registerAction : self._removeDevice(action.device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1164, in destroyDevice : self.devicetree.registerAction(action) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2155, in newDevice : self.destroyDevice(container) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1734, in on_add_clicked : disks=disks) :ValueError: Cannot remove non-leaf device 'fedora'
Created attachment 637547 [details] File: anaconda-tb
Created attachment 637548 [details] File: environ
Created attachment 637549 [details] File: type
Created attachment 637550 [details] File: ifcfg.log
Created attachment 637551 [details] File: storage.log
Created attachment 637552 [details] File: version
Created attachment 637553 [details] File: program.log
Created attachment 637554 [details] File: executable
Created attachment 637555 [details] File: product
Created attachment 637556 [details] File: anaconda.log
Created attachment 637557 [details] File: hashmarkername
Created attachment 637558 [details] File: cmdline_file
Created attachment 637559 [details] File: release
Created attachment 637560 [details] File: messages
Attempting to reproduce Bug 868505. Package: anaconda-18.27-1.fc18.x86_64 OS Release: Fedora release 18
Created attachment 640605 [details] [18.27 log anaconda-tb-rzlVWX] ValueError: Cannot remove non-leaf device 'fedora' Reproduced with 18.27: anaconda 18.27 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 374, in _removeDevice raise ValueError("Cannot remove non-leaf device '%s'" % dev.name) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 424, in registerAction self._removeDevice(action.device) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1164, in destroyDevice self.devicetree.registerAction(action) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2174, in newDevice self.destroyDevice(container) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1749, in on_add_clicked disks=disks) ValueError: Cannot remove non-leaf device 'fedora' Local variables in innermost frame: force: None self: <pyanaconda.storage.devicetree.DeviceTree object at 0x4f2aa10> moddisk: True dev: non-existent 7036MB lvmvg fedora (21)
This procedure appears to be a reproducer: Start with a 12 GB disc image with default partitioning. Proceed to Manual Partitioning. Remove all pre-existing partitions. Auto-create new partitions. Remove Root partition. Create Root partition with capacity 3000. Create Home, but leave capacity empty. The exception occurs when 'Add mount point' is clicked. A corresponding log file is attached with Comment 16. Tested with: anaconda-18.27-1.fc18 Fedora-18-Beta-TC7-x86_64-Live-Desktop.iso Command-line: $ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Beta/TC7/Fedora-18-Beta-TC7-x86_64-Live-Desktop.iso -usb -vga qxl -boot menu=on -usbdevice mouse
(In reply to comment #17) ... > Start with a 12 GB disc image with default partitioning. ... $ qemu-img create f18-test-2.img 12G Start installer from Live CD in a VM. Click Installation Destination. Click Done. Click Begin Installation. Allow installation to complete. Click Reboot to exit installer.
(In reply to comment #17) > This procedure appears to be a reproducer: > ... Starting with an empty disc image is sufficient. Here is a simpler reproducer: $ qemu-img create f18-test-2.img 12G Start installer from Live CD in a VM. Click Installation Destination. Proceed to Manual Partitioning. Auto-create new partitions. Remove Root partition. Add Root mount point with capacity 3000. Add Home mount point, but leave capacity empty. The exception occurs when 'Add mount point' is clicked.
I have a system I'm moving from F17 x86_64 to F18 x86_64. It's a KVM guest I'm using to test the process before I use it on my actual workstation, where I have a similar setup. Current partition setup is approximately: * /dev/vda1 - 500MB - /boot * /dev/vda2 - 11500MB - PV (one VG only) * LV - 4500MB - / * LV - 2000MB - swap * LV - 5000MB - /home I believe this is a fairly common scenario for a previous Fedora installation. I selected the "let me do my own partitioning" option to reclaim space, because I want to keep /home intact. I followed this process: 1. Use '-' to remove /boot, use '+' to recreate for new installation. Swap was automatically reused. 2. Reassign /home to new installation by giving it the same mount point and hitting 'Apply changes'. 3. Use '-' to remove / 4. Use '+' to recreate / and entered mount point and size 5. Traceback. Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7
(In reply to comment #20) > I have a system I'm moving from F17 x86_64 to F18 x86_64. It's a KVM guest > I'm using to test the process before I use it on my actual workstation, > where I have a similar setup. Current partition setup is approximately: > > * /dev/vda1 - 500MB - /boot > * /dev/vda2 - 11500MB - PV (one VG only) > * LV - 4500MB - / > * LV - 2000MB - swap > * LV - 5000MB - /home > > I believe this is a fairly common scenario for a previous Fedora > installation. I selected the "let me do my own partitioning" option to > reclaim space, because I want to keep /home intact. I followed this process: > > 1. Use '-' to remove /boot, use '+' to recreate for new installation. Swap > was automatically reused. > 2. Reassign /home to new installation by giving it the same mount point and > hitting 'Apply changes'. > 3. Use '-' to remove / > 4. Use '+' to recreate / and entered mount point and size > 5. Traceback. > There is no support for adding new lvs to existing vgs as of now. What you probably want to do is just reformat /boot and / instead of deleting and then recreating them. I know that was your only option at alpha time, but now there's a "Reformat" checkbox under the "Customize" expander, next to the filesystem type dropdown menu. Either way, this traceback will be gone in the beta.
I am hoping this ends up the same bug as 868505.
The process in comment #21 gets me the desired results -- thanks for the pointer.
Created BIOS boot Created Swap Tried creating / that was supposed to expand across the rest of the disk, got the error. Package: anaconda-18.27 OS Release: Fedora release 18
Discussed at 2012-11-12 QA meeting acting as a blocker review meeting. Accepted as a blocker per criterion "The installer's custom partitioning mode must be capable of the following ... Rejecting obviously invalid operations without crashing"
anaconda-18.29-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.29-1.fc18
I have reproduced the issue according to comment 17 with F18 Beta TC8, but everything worked well with smoke18 (anaconda 18.29). Setting to verified.
Removed existing (Windows) partitions, added custom ones. Did the exact same thing a moment ago and it didn't crash - so not sure how to exactly reproduce this. Package: anaconda-18.28-1.fc18.x86_64 OS Release: Fedora release 18
Package anaconda-18.29-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.29-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-18105/anaconda-18.29-1.fc18 then log in and leave karma (feedback).
anaconda-18.29-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.