1.boot Fedora-Workstation-Live-42-20250315.n.0.x86_64.iso on a VM with one disk 2 create /boot /boot/efi and a rootfs with LUKS2 3 reformat root partition and "reusing existing encryption" 4 after "return to installation" is clicked, warning pops up,claiming "luks device vda3 can't be reused for installation without an encryption key specified for the device" though I did input the password. If you delete that rootfs and then create an encrypted rootfs again, you will end up with another warning(screenshot), if you create a non-encrypted rootfs, you will see "you have not defined a root partition(/),which is required for installation of fedora to continue", but / is right there.Just the same as :https://bugzilla.redhat.com/show_bug.cgi?id=2353524 Please note this is also 100% reproducible with the latest anaconda-webui:anaconda-webui-28-1.fc42.noarch Reproducible: Always
Created attachment 2081599 [details] anaconda.log
Created attachment 2081600 [details] storage.log
Created attachment 2081601 [details] screencast
Created attachment 2081602 [details] screenshot
This is an issue with cockpit-storage not handling out passwords when 'Reuse existing encryption' code path is followed. Changing the component to cockpit-storage.
Proposed as a Blocker for 42-final by Fedora user lnie using the blocker tracking app because: It seems affects the "Remove a planned storage volume from the planned layout" part of https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria#Custom_partitioning
https://github.com/cockpit-project/cockpit/pull/21755
Discussed during the 2025-03-24 blocker review meeting [1]: * AGREED: 2354497 - AcceptedBlocker (Final) - this is accepted as a violation of "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration" (can also be argued to violate the Beta custom partitioning criteria) [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-24/f42-blocker-review.2025-03-24-16.02.log.html
FEDORA-2025-57cefcbc36 (cockpit-336.1-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-57cefcbc36
FEDORA-2025-e04b83d15b (cockpit-336.1-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-e04b83d15b
FEDORA-2025-57cefcbc36 (cockpit-336.1-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
The interesting release here is F42, not rawhide.
FWIW, to avoid this kinda issue, when creating updates for multiple releases, I *unset* the "close bug on stable" setting, then re-enable it for *only* the update that's for the release I actually want to close the bug. I realize this might be tricky if you're using automation, though.
FEDORA-2025-e04b83d15b (cockpit-336.1-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
sorry for the a bit late reply, I'm pretty busy with other stuff. This bug seems still there: I boot Fedora-Workstation-Live-42-20250315.n.0.x86_64.iso and update cockpit to latest cockpit-336.1-1.fc42,but I still could reproduce it.
Turns out dnf cockpit didn't have cockpit-storaged(while Katerina's fix is) installed by default,closing.