Created attachment 1312357 [details] Configure volume group window Description of problem: By default the installer proposed some logical volumes for the installation of Fedora 26. By default it also suggests to encrypt those volumes. I disabled the encryption and confirmed the change, then changed my mind and tried to turn it back on. This gives a "device reconfiguration failed" error, asking for details just spawns an empty window with a close button. Anaconda didn't go down entirely and in the end I managed to work around this by disabling encryption just once on one logical volume, so that only the logical volume on my HDD which housed my /home directory was encrypted. Version-Release number of selected component (if applicable): The Anaconda version shipped with Fedora 26. How reproducible: I'm on a PC with both one SSD and one HDD and chose a clean installation, overwriting any existing OS's (just Fedora 24). I think this might be related to the issue. Open a LVM logical volume in the manual partitioning, disable encryption. Then open it again and enable encryption. Now receive the error message. Steps to Reproduce: 1. Install on a PC with one HDD and one SSD, overwrite any existing OS's. 2. In manual partitioning, pick LVM and open a logical volume. 3. Disable encryption and apply the change. 4. Open it again, enable encryption and apply the change. 5. See the error message. Actual results: "Device reconfiguration failed" error with unspecified details. Expected results: No crash, disabling and enabling shouldn't cause issues. Additional info: None.
Created attachment 1312358 [details] Error message details, from link in yellow bar
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.