Description of problem: I tried to verify bug 1163410 comment 3 (using TC2 and that update.img). In manual partitioning, I selected an existing ext4 partition and tried to shrink it. Crashed after clicking on Update Settings. Version-Release number of selected component: anaconda-core-21.48.14-1.fc21.x86_64 The following was filed automatically by anaconda: anaconda 21.48.14-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 725, in _handle_size_change size = self.alignTargetSize(size) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 121, in decorated return func(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1145, in _save_right_side self._handle_size_change(size, old_size, device, use_dev) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2531, in on_update_settings_clicked self._save_right_side(self._current_selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/utils.py", line 240, in _run_once_one_arg self._func(*args, **kwargs) AttributeError: 'CustomPartitioningSpoke' object has no attribute 'alignTargetSize' Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base --updates=https://dlehman.fedorapeople.org/updates/updates-1163410.1.img cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Workstation-x86_64-2 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.17.2-300.fc21.x86_64 other involved packages: anaconda-gui-21.48.14-1.fc21.x86_64 product: Fedora" release: Fedora release 21 (Twenty One) type: anaconda version: Fedora
Created attachment 957476 [details] File: anaconda-tb
Created attachment 957477 [details] File: anaconda.log
Created attachment 957478 [details] File: environ
Created attachment 957479 [details] File: journalctl
Created attachment 957480 [details] File: lsblk_output
Created attachment 957481 [details] File: nmcli_dev_list
Created attachment 957482 [details] File: os_info
Created attachment 957483 [details] File: storage.log
Created attachment 957484 [details] File: ifcfg.log
Created attachment 957485 [details] File: packaging.log
Created attachment 957486 [details] File: program.log
Fixed on f21-branch in commit 32f10c34ebe200da.
This seems fixed in https://admin.fedoraproject.org/updates/python-blivet-0.61.10-1.fc21,anaconda-21.48.15-1.fc21 .
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.