Bug 2236398

Summary: webUI: cannot install to encrypted software RAID partition
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 39CC: anaconda-maint, awilliam, hricky, jkonecny, robatino, vslavik, vtrefny, w
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard: AcceptedBlocker
Fixed In Version: anaconda-39.32.3-1.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 05:23:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2231339, 2187792    
Attachments:
Description Flags
screencast1
none
screencast2
none
screencast
none
screencast4
none
anaconda.log
none
storage.log none

Description lnie 2023-08-31 07:13:23 UTC
As shown in the screencasts, error message pops up if we created one encrypted software raid partition(screencast1).The error message says we need rescan the disks,but after we rescan the disks,the software-raid device will not be listed when we set mount point,just as described in #2236356.
We will also run into similar problem if we want to use encrypted lvm partitions,but will be able to finish the installation in that situation. The differences are ,as you can see from the screencast3 and screencast4,1)anaconda will ask users to de-encrypt the partitions,2)the partitions will be shown.

Reproducible: Always

Comment 1 lnie 2023-08-31 07:24:32 UTC
Created attachment 1986251 [details]
screencast1

Comment 2 lnie 2023-08-31 07:25:44 UTC
Created attachment 1986252 [details]
screencast2

Comment 3 lnie 2023-08-31 07:30:28 UTC
Created attachment 1986253 [details]
screencast

Comment 4 lnie 2023-08-31 07:33:19 UTC
Created attachment 1986254 [details]
screencast4

Comment 5 lnie 2023-08-31 07:39:52 UTC
Created attachment 1986255 [details]
anaconda.log

Comment 6 lnie 2023-08-31 07:40:47 UTC
Created attachment 1986256 [details]
storage.log

Comment 7 Fedora Blocker Bugs Application 2023-09-01 09:14:59 UTC
Proposed as a Blocker for 39-beta by Fedora user lnie using the blocker tracking app because:

 This bug violates  the criteria: 
https://fedoraproject.org/wiki/Fedora_39_Beta_Release_Criteria#Custom_partitioning

Comment 8 Hristo Marinov 2023-09-01 17:01:12 UTC
Looks like Bug 2236538

Comment 9 Adam Williamson 2023-09-04 15:38:18 UTC
+4 in https://pagure.io/fedora-qa/blocker-review/issue/1246 , accepted.

Comment 10 Adam Williamson 2023-09-06 15:53:03 UTC
Lili was testing with a slightly old image, but I can confirm this on yesterday's Rawhide, with the latest anaconda build. It behaves just as she described. Trying to set an encrypted RAID device as the root partition and hitting Next shows the red error box, which in English reads:

"The existing unlocked LUKS device blivet cannot be used for the installation without an encryption key specified for this device. Please, rescan the storage."

but if you go back to the "Installation method" screen and rescan the storage, then return to the mount point assignment screen, the same error message is still shown, and now the encrypted RAID device does not appear in the drop-down menu of possible mount point targets at all.

Comment 11 Vojtech Trefny 2023-09-08 10:42:51 UTC
*** Bug 2236538 has been marked as a duplicate of this bug. ***

Comment 12 Vojtech Trefny 2023-09-08 11:09:35 UTC
upstream PR: https://github.com/rhinstaller/anaconda/pull/5146

updates image for Fedora 39: https://vtrefny.fedorapeople.org/img/rhbz2236398.img

Comment 13 Adam Williamson 2023-09-08 20:45:30 UTC
OK, looks like it's fixed to me. Thanks!

Comment 14 Adam Williamson 2023-09-12 21:48:37 UTC
As webUI has been deferred to F40 and this bug is specific to the webUI flow, it is clearly no longer a blocker.

Comment 15 Adam Williamson 2023-09-12 22:08:08 UTC
actually, the logical thing to do is to defer the blocker status to F40, I guess.

Comment 16 Fedora Update System 2023-09-18 15:46:03 UTC
FEDORA-2023-7aa321caa4 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7aa321caa4

Comment 17 Fedora Update System 2023-09-19 01:11:14 UTC
FEDORA-2023-7aa321caa4 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-7aa321caa4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7aa321caa4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 18 Fedora Update System 2023-09-22 00:18:56 UTC
FEDORA-2023-7aa321caa4 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 lnie 2023-09-22 01:05:35 UTC
The updates is for gtk ui,while this bug is about web ui,reopening.

Comment 20 Vojtech Trefny 2023-09-22 05:23:36 UTC
The fix for this issue is included in the 39.32.3-1 anaconda release[1]. The anaconda-webui package is still available in Fedora 39 so (some) fixes for the Web UI are still being released for it.


[1] https://github.com/rhinstaller/anaconda/releases/tag/anaconda-39.32.3-1