1.Boot Fedora-Workstation-Live-42_Beta-1.4.x86_64.iso on a VM which contains 3 disks 2.select all the disks, launch storage editor 3. create /boot /boot/efi partition and then an mdraid partition 4. Return to Installation 5. click "Mount point assignment" to set mount point,but found the screen is blinking,and you won't be able to assign a mount point Reproducible: Always
Created attachment 2080016 [details] anaconda.log
Created attachment 2080017 [details] storage.log
@lnie please specify what exactly you did with the storage editor. Is it RAID on top of disks, on top of partitions etc? Also what's on the RAID device? Did you create a partition table on that or format it directly?
Created attachment 2080020 [details] screencast
It is RAID on top of disks,and I created partition table on that, then a partition, please check the attached the screencast for more info,thanks.
I am able to reproduce this, this need to be proposed as a final blocker. As workaround would be currently to set the mount points when creating the MDraid partitions in the storage editor.
Confirmed the workaround. Gonna to propose it as a Beta blocker,as it violates: https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria#Custom_partitioning
Proposed as a Blocker for 42-beta by Fedora user lnie using the blocker tracking app because: This violates: https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria#Custom_partitioning
Upstream fix: https://github.com/rhinstaller/anaconda/pull/6261
And the corresponding front-end test: https://github.com/rhinstaller/anaconda-webui/pull/699
Discussed at Go/No-Go meeting [1]: !agreed 2351848 - RejectedBlocker (Beta) - we decided this is a conditional violation (the installer can do everything the criteria say if you hold it right, but it fails if you hold it wrong). Given webui is new and we have to accept some level of teething troubles for it in a Beta, we decided this is not severe enough to be a blocker, so it's rejected [1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-13/f42-beta-go-no-go-meeting.2025-03-13-17.02.log.html Re-proposing it as a Final blocker instead.
FEDORA-2025-57c36dc467 (anaconda-42.27.4-1.fc42 and anaconda-webui-27-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-57c36dc467
FEDORA-2025-57c36dc467 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-57c36dc467` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-57c36dc467 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Discussed during the 2025-03-17 blocker review meeting [1]: * AGREED: 2351848 - AcceptedBlocker (Final) - this is accepted as a conditional violation of "Assign mount points to existing storage volumes", in the case that you're using webUI and the 'existing storage volume' is a RAID device (possibly only one you just created in the storage editor) [1] https://meetbot-raw.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-17/f42-blocker-review.2025-03-17-16.00.log.html
FEDORA-2025-57c36dc467 (anaconda-42.27.4-1.fc42 and anaconda-webui-27-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.