Description of problem: Changed harddisk settings during installation process. Version-Release number of selected component: anaconda-20.25.15-1 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 829, in initializeDisk raise ValueError("cannot initialize a disk that has partitions") File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2134, in _destroy_device self.__storage.initializeDisk(device.disk) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2241, in on_remove_clicked self._destroy_device(dev) ValueError: cannot initialize a disk that has partitions Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora\x2020\x20x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20 Potential duplicate: bug 1023903
Created attachment 912292 [details] File: anaconda-tb
Created attachment 912293 [details] File: anaconda.log
Created attachment 912294 [details] File: environ
Created attachment 912295 [details] File: lsblk_output
Created attachment 912296 [details] File: nmcli_dev_list
Created attachment 912297 [details] File: os_info
Created attachment 912298 [details] File: program.log
Created attachment 912299 [details] File: storage.log
Created attachment 912300 [details] File: syslog
Created attachment 912301 [details] File: ifcfg.log
Created attachment 912302 [details] File: packaging.log
What do you mean by "Changed harddisk settings"? Did you rescan the disk in anaconda afterwards? Is this issue still reproducible with F21 or F22?
Hej David, it's already a long time ago since I reported this. :-) As far as I can remember, I tried to change the partition layout after automatic configuration. In the next weeks I'm very busy and haven't any time to test it. But as soon as possible I'll try it and leave you a message here.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Can't reproduce this in F22 anymore.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.