Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2396646 ** Information from BlockerBugs App:
The votes have been last counted at 2025-09-23 07:35 UTC and the last processed comment was #comment-986913
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
This seems more like a freeze exception.
FinalFE +1
FinalBlocker +1 For a different reason than cited in the bug:
the installer must be able to: Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions
Oddly, I don't really see an installation criteria for disk encryption. The closest I can find is this post-install basic criteria which pretty explicitly doesn't mention upgrades.
This does feel like a pretty easy path to unintended data loss though.
FinalBlocker +1 FinalFE +1
Based on Beta's Criteria, which I believe is valid because of final criteria stating "All Fedora 43 Beta Release Criteria must be met."
I believe this violates "Assign mount points to existing storage volumes" at https://fedoraproject.org/wiki/Fedora_43_Beta_Release_Criteria#Custom_partitioning
FinalBlocker +1
I clarified the bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=2396646#c6
Given that using the whole disk device for a filesystem, instead of using partitions, is possibly quite a niche use case, there is no data loss, and this layout is definitely not offered by default, I'm not completely sure whether this qualifies as a blocker. Even though the criterion says:
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. https://fedoraproject.org/wiki/Fedora_43_Final_Release_Criteria#Disk_layouts
So yes, it should be covered... but still feels quite an obscure use case for me.
FinalFE +1 FinalBlocker 0
Based on my assumption that there is one partition spread across the entire disk with an encrypted filesystem mounted as /home. It should definitely be reusable, as the above seems a perfect use case to have.
AGREED AcceptedFinalBlocker
Discussed at the 2025-09-22 (blocker / freeze exception) review meeting:
This is accepted as a violation of "the installer must be able to: ... Assign mount points to existing storage volumes", noting the "Re-using /home" footnote below, in the specific case that the /home to be reused is both encrypted and a direct-on-disk filesystem (not a partition). This is a fairly uncommon case but we decided it was potentially common enough (given the webui's ability to create such a layout) that we should block on it.
https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2025-09-22/f43-blocker-review.2025-09-22-16.01.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.