Version-Release number of selected component: anaconda-21.48.6-1 The following was filed automatically by anaconda: anaconda 21.48.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 767, in configure raise(e) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1752, in _destroy_device factory.configure() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 122, in decorated return func(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1808, in on_remove_clicked self._destroy_device(device) DeviceFactoryError: new size must of type Size Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-WS-21_A_T7-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.16.1-301.fc21.x86_64 product: Fedora-Workstation release: Cannot get release name. type: anaconda version: 21_Alpha_TC7
Created attachment 937501 [details] File: anaconda-tb
Created attachment 937502 [details] File: anaconda.log
Created attachment 937503 [details] File: environ
Created attachment 937504 [details] File: lsblk_output
Created attachment 937505 [details] File: nmcli_dev_list
Created attachment 937506 [details] File: os_info
Created attachment 937507 [details] File: program.log
Created attachment 937508 [details] File: storage.log
Created attachment 937509 [details] File: syslog
Created attachment 937510 [details] File: ifcfg.log
Created attachment 937511 [details] File: packaging.log
Fixed on rawhide (will be in anaconda-22.6). I'll propose as a blocker for f21 before the week is over.
Discussed in 2014-09-24 Blocker Review meeting [1]. Accepted as a blocker. This is a clear blocker violating the Beta criterion: "must be able to remove existing volumes." [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-09-24/
anaconda-21.48.8-1.fc21, python-blivet-0.61.3-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/python-blivet-0.61.3-1.fc21,anaconda-21.48.8-1.fc21
Package anaconda-21.48.8-1.fc21, python-blivet-0.61.3-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-21.48.8-1.fc21 python-blivet-0.61.3-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-11977/python-blivet-0.61.3-1.fc21,anaconda-21.48.8-1.fc21 then log in and leave karma (feedback).
Package anaconda-21.48.8-1.fc21, python-blivet-0.61.3-1.fc21, pykickstart-1.99.60-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-21.48.8-1.fc21 python-blivet-0.61.3-1.fc21 pykickstart-1.99.60-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-11977/pykickstart-1.99.60-2.fc21,python-blivet-0.61.3-1.fc21,anaconda-21.48.8-1.fc21 then log in and leave karma (feedback).
Should be fixed in 21 Beta TC2, we can test there.
anaconda-21.48.8-1.fc21, python-blivet-0.61.3-1.fc21, pykickstart-1.99.60-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Another user experienced a similar problem: Description: I have a hd with two partitions one with windows 7 and another clean to install fedora 21 workstation beta TC4. Was automatically created mount points on custom partition using free space, but when I deleted the /home occurred this problem; Steps: 1. previous system installed; 2. boot (live-usb) fedora workstation beta tc4 for install with free space; 3. disk partition method custom and then select automatic creation of mount points (/boot, /home, / and swap) 4. delete /home (only) Expect results: delete /home and follow the installation normally. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=ext4 ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 3.17.0-301.fc21.x86_64 other involved packages: python-blivet-0.61.5-1.fc21.noarch, anaconda-gui-21.48.10-1.fc21.x86_64 package: anaconda-core-21.48.10-1.fc21.x86_64 packaging.log: product: Fedora" reason: DeviceFactoryError: _removeDevice() got an unexpected keyword argument 'moddisk' release: Fedora release 21 (Twenty One) version: Fedora
Another user experienced a similar problem: Reinstalling laptop, I used fdisk to wipe my existing Linux partitions, then rebooted. Started Installation, did a automatic partition, attempted to shrink /home partition, it failed. Got error. addons: com_redhat_kdump cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-21-x86_64 quiet ip=dhcp ks=ftp://172.18.2.7/fedora-x86_64.cfg hashmarkername: anaconda kernel: 3.17.1-302.fc21.x86_64 package: anaconda-21.48.10-1 product: Fedora" reason: DeviceFactoryError: _removeDevice() got an unexpected keyword argument 'moddisk' release: Cannot get release name. version: Fedora
Bruno: Shawn: what you guys hit doesn't actually look like the same thing the initial report here is for (though libreport decided it was a dupe, for some reason). The initial traceback is: DeviceFactoryError: new size must of type Size You guys are hitting: DeviceFactoryError: _removeDevice() got an unexpected keyword argument which does not seem to be the same thing. If you can reproduce this, can you please save the logs from /tmp - at least the anaconda-tb file, which has the actual traceback in it, and storage.log - and file a new bug with them attached? Thanks.
The bug Shawn and Bruno hit is https://bugzilla.redhat.com/show_bug.cgi?id=1154050 , it should be fixed in Beta RC1.