Bug 2346436

Summary: "EFI System Partition" does not show in available filesystems for custom installs since blivet 3.12.0
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: anacondaAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 42CC: anaconda-maint, blivet-maint-list, dlehman, kkoukiou, kparal, mkolman, robatino, rvykydal, vtrefny, w
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: openqa AcceptedBlocker
Fixed In Version: anaconda-42.27.3-1.fc42 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-03-10 16:14:00 UTC Type: Bug
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: 2291263    

Description Adam Williamson 2025-02-19 00:51:41 UTC 
Since python-blivet-3.12.0 landed in F42 and Rawhide on 2025-02-15, all custom installs to UEFI are failing in openQA because "EFI System Partition" does not seem to be shown as an available filesystem type, so we can't create an ESP (which is needed for a UEFI install). *Automatic* UEFI installs do seem to work OK (and really are installing in UEFI mode, I checked). Also, the "Click here to create them automatically" option in the "custom" workflow works, and creates an EFI system partition. The issue really seems to be limited to the 'discovery' of what filesystems are available when manually specifying one.

This is affecting both "custom" (anaconda's own custom mode) and "advanced custom" (blivet-gui), though most of the "custom" tests pass because they use the "create them automatically" workflow.

Proposing as a Beta release blocker as a violation of the custom partitioning criteria, because this makes it impossible to complete an install to UEFI using the 'advanced custom' workflow, unless you have an existing ESP to reuse.
Comment 1 Vojtech Trefny 2025-02-19 10:41:41 UTC 
Moving to Anaconda, PR with proposed fix: https://github.com/rhinstaller/anaconda/pull/6190
Comment 2 Adam Williamson 2025-02-23 19:28:06 UTC 
+4 in https://pagure.io/fedora-qa/blocker-review/issue/1758 , marking accepted.
Comment 3 Fedora Update System 2025-03-06 10:22:38 UTC 
FEDORA-2025-73a6f8a23c (anaconda-42.27.3-1.fc42 and anaconda-webui-26-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-73a6f8a23c
Comment 4 Fedora Update System 2025-03-07 08:35:05 UTC 
FEDORA-2025-73a6f8a23c 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-73a6f8a23c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-73a6f8a23c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Kamil Páral 2025-03-07 14:50:29 UTC 
With Fedora-Server-dvd-x86_64-42_Beta-1.2.iso , I can create ESP manually in both custom and blivet disk config. This seems resolved.
Comment 6 Fedora Update System 2025-03-10 16:14:00 UTC 
FEDORA-2025-73a6f8a23c (anaconda-42.27.3-1.fc42 and anaconda-webui-26-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.