Description of problem: On /boot I have the vmlinuz+initrd.img pair and install.img. Anaconda shouldn't crash but tell me I can't delete this device. Version-Release number of selected component: anaconda-24.6-1 The following was filed automatically by anaconda: anaconda 24.6-1 exception report Traceback (most recent call first): File "/usr/lib/python3.4/site-packages/blivet/blivet.py", line 1087, in destroyDevice raise ValueError("cannot modify protected device") File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1844, in _destroy_device self._storage_playground.destroyDevice(device) File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 136, in decorated return func(*args, **kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1969, in on_remove_clicked self._destroy_device(device) ValueError: cannot modify protected device Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: inst.stage2=hd:sda1:/install.img repo=https://kojipkgs.fedoraproject.org/mash/rawhide-20151111/rawhide/x86_64/os vnc dnf.rpm.log: Nov 11 12:45:55 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.4.0-0.rc0.git6.1.fc24.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide
Created attachment 1092686 [details] File: anaconda-tb
Created attachment 1092688 [details] File: anaconda.log
Created attachment 1092689 [details] File: dnf.log
Created attachment 1092690 [details] File: environ
Created attachment 1092691 [details] File: lsblk_output
Created attachment 1092692 [details] File: nmcli_dev_list
Created attachment 1092693 [details] File: os_info
Created attachment 1092694 [details] File: program.log
Created attachment 1092695 [details] File: storage.log
Created attachment 1092696 [details] File: syslog
Created attachment 1092697 [details] File: ifcfg.log
Created attachment 1092698 [details] File: packaging.log
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.