Description of problem: I guess it was triggered like this: 1. Go to partitioning screen, select a disk, Done, confirm automatic partitioning (erase all contents). 2. Go back to partitioning screen, unselect the disk, Done. 3. Go back to partitioning screen, select the disk again, Done, crash. Version-Release number of selected component: anaconda-23.17-1 The following was filed automatically by anaconda: anaconda 23.17-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.4/site-packages/parted/disk.py", line 259, in addPartition constraint.getPedConstraint()) File "/usr/lib64/python3.4/site-packages/parted/decorators.py", line 42, in new ret = fn(*args, **kwds) File "/usr/lib/python3.4/site-packages/blivet/formats/disklabel.py", line 298, in addPartition constraint=constraint) File "/usr/lib/python3.4/site-packages/blivet/devices/partition.py", line 502, in addHook self.partedPartition.type) File "/usr/lib/python3.4/site-packages/blivet/devicetree.py", line 523, in unhide hidden.addHook(new=False) File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 799, in on_back_clicked self.storage.devicetree.unhide(disk) _ped.PartitionException: Can't have overlapping partitions. Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-23_A-x86_64 quiet dnf.rpm.log: Aug 06 10:00:50 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.2.0-0.rc5.git0.2.fc23.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 23
Created attachment 1059781 [details] File: anaconda-tb
Created attachment 1059782 [details] File: anaconda.log
Created attachment 1059783 [details] File: dnf.log
Created attachment 1059784 [details] File: environ
Created attachment 1059785 [details] File: lsblk_output
Created attachment 1059786 [details] File: nmcli_dev_list
Created attachment 1059787 [details] File: os_info
Created attachment 1059788 [details] File: storage.log
Created attachment 1059789 [details] File: syslog
Created attachment 1059790 [details] File: ifcfg.log
Created attachment 1059791 [details] File: packaging.log
Created attachment 1059792 [details] File: program.log
Probably will be fixed by this patch set -- https://github.com/rhinstaller/anaconda/pull/257
updates.img for testing the changes from the above mentioned PR: http://vpodzime.fedorapeople.org/1250875_updates.img (for anaconda-23.18-1 or newer)
(In reply to Vratislav Podzimek from comment #14) > updates.img for testing the changes from the above mentioned PR: > > http://vpodzime.fedorapeople.org/1250875_updates.img > (for anaconda-23.18-1 or newer) That seems to fix the bug.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Patch from comment 13 seems pushed.