Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2391723 ** Information from BlockerBugs App:
Commented but haven't voted yet: supakeen, kashyapc, lruzicka
The votes have been last counted at 2026-03-16 17:47 UTC and the last processed comment was #comment-1008496
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
First, do we have a criterion to boot the ISO on 32-bit efi on 64-bit systems or is it best effort? I couldn't find one from a quick scan around the criteria and the one that came closest was:
Release-blocking images must boot from all system firmware types that are commonly found on the primary architectures.
The image-builder produced ISO (currently: only Fedora IoT) that are part of the Fedora compose are have never included shim-ia32 previously.
From a cursory review this was reverted and fixed up in kiwi. It would still need to be reverted in lorax and potentially implemented in image-builder (there's a re-opened PR to introduce this functionality which will likely make it into next weeks release, so before the final freeze)?
I am a weak -1 FinalBlocker, +1 FinalFE; I don't think the setup is that common and many of the artifacts work.
The ones that wouldn't work (that I'm aware of) are the everything/server network installer/dvd installer (produced by lorax) and the Fedora IoT ISO (produced by image-builder).
FinalFE +1
Reading the issue, it is still not immediately clear to me which deliverables don't work with 32 bit UEFIs. I'm inclined to err on the side of caution.
FinalBlocker +1 FinalFE +1
May need to discuss this in the QA meeting for any clarification.
Small update to this issue is that image-builder 53 (currently in bodhi testing) has addressed the issue for the ISOs (IoT and any future ones) it produces as well.
image-builder
FinalFE +1 AGREED AcceptedFinalFE
The following votes have been closed:
People are still using x86_64 with 32 bit UEFI; it only makes sense to have it as part of the FE. Reading the bug, the erroneous commit is reverted
AGREED AcceptedFinalBlocker
Discussed at the 2026-03-16 (blocker / freeze exception) review meeting:
This is accepted as a violation of "All release-blocking images must boot in their supported configurations" in the case of x86_64 systems with 32-bit UEFI firmwares. Our subjective decision was that this is a significant enough class of systems to constitute a release blocking bug. Note we accept this only in the context of 'making an effort to support such systems', as the fix is relatively straightforward. We don't necessarily intend to establish a precedent that any kind of bug in this unusual path becomes a blocker; one that required more work by the developers may not reach the bar.
https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-03-16/f44-blocker-review.2026-03-16-16.01.log.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F44 is no longer tracked by BlockerBugs, closing this ticket.