Description of problem: When creating new partition in manual partitioning, set drive size to greater than size of disk (611 GB out of 500 GB on disc). Goal was to occupy maximum space; received value error instead. This was in selector, not when writing to disc. Additional details: Disk free: approx 150 GB Several other file systems present on disc, including NTFS, ext4, and UEFI BIOS Drive was to be created as ext4 Version-Release number of selected component: anaconda-core-27.20.4-4.fc27.x86_64 The following was filed automatically by anaconda: anaconda 27.20.4-1 exception report Traceback (most recent call first): File "/usr/lib/python3.6/site-packages/blivet/deviceaction.py", line 448, in __init__ raise ValueError("new size same as old size") File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/blivet.py", line 1190, in resize_device actions.append(ActionResizeDevice(device, new_size)) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/custom_storage.py", line 814, in _handle_size_change self._storage_playground.resize_device(use_dev, use_size) File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/custom_storage.py", line 133, in decorated return func(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/custom_storage.py", line 1222, in _save_right_side self._handle_size_change(size, old_size, device) File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/custom_storage.py", line 2779, in on_update_settings_clicked self._save_right_side(self._accordion.current_selector) File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/utils.py", line 267, in _run_once_one_arg self._func(*args, **kwargs) ValueError: new size same as old size Additional info: addons: com_redhat_kdump blivet-gui-utils.log: cmdline: /usr/libexec/system-python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-27-1-6 rd.live.image quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.13.9-300.fc27.x86_64 other involved packages: python3-blivet-2.1.11-3.fc27.noarch, anaconda-gui-27.20.4-4.fc27.x86_64 product: Fedora release: Fedora release 27 (Twenty Seven) type: anaconda version: 27
Created attachment 1427902 [details] File: anaconda-tb
Created attachment 1427903 [details] File: anaconda.log
Created attachment 1427904 [details] File: environ
Created attachment 1427905 [details] File: journalctl
Created attachment 1427906 [details] File: lsblk_output
Created attachment 1427907 [details] File: nmcli_dev_list
Created attachment 1427908 [details] File: os_info
Created attachment 1427909 [details] File: program.log
Created attachment 1427910 [details] File: storage.log
Created attachment 1427911 [details] File: ifcfg.log
*** Bug 1614462 has been marked as a duplicate of this bug. ***
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/1577
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.