Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2357214 ** Information from BlockerBugs App:
Commented but haven't voted yet: lbrabec
The votes have been last counted at 2025-04-07 17:55 UTC and the last processed comment was #comment-964618
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 got moved from #1828 to here.
FinalBlocker +1
Feels like a violation of the disk layouts criteria.
This sounds quite serious, because if you re-create MDRAID (e.g. if you made an error in the RAID level), anaconda works with an assumption that the device has a different size. That might cause and causes a number of filesystem-related errors and data corruption.
Discussed during the 2025-04-07 blocker review meeting [1]:
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-04-07/f42-blocker-review.2025-04-07-16.01.log.html
AGREED AcceptedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F42 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.