Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2243206 ** Information from BlockerBugs App:
The votes have been last counted at 2023-10-16 15:21 UTC and the last processed comment was #comment-879194
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 does not come under the criteria, AFAICT. In https://fedoraproject.org/wiki/Basic_Release_Criteria#Release-blocking_images_must_boot , we say "Release-blocking live and dedicated installer images must boot when written to a USB stick with at least one of the officially supported methods." The "officially supported methods" are all about writing images to a stick with a dd-style method and intend for the stick to be used as a dedicated install medium. I don't think we have any language that considers the install methods affected by this bug "supported".
FinalBlocker -1
This comes under https://fedoraproject.org/wiki/Basic_Release_Criteria#Disk_selection under conditions mentioned in BZ#2243206, a user will be shown an error: "Requested boot drive /dev/sda doesn't exist or cannot be used"
This is regression as it is working in previous releases
If a user clears existing /boot or / partitions as part of %pre, it will render the system unbootable (talking from experience).
My point is that installation media protection should not extend beyond the partition the installation media is located on, let the user decide what disk they want to protect in kickstart i.e. ignoredisk --only-use=sdb
FinalBlocker +1
@tdabasin the preamble to that section states "Except where otherwise specified, each of these requirements applies to all supported configurations described above." IMO this bug does not affect a "supported configuration", as I explained in my previous comment.
Regression? Yes. Blocker? Not by the criteria. Though now that I see it was possible, I wish it worked so I could do installs this way in the future...
Apart of this criterion thing, I even believe that the general principle to install is that I use one medium as a source and and another as a target. I understand that to use one medium for everything is "cute", but I think that only a small group of users might be actually affected by this.
AGREED RejectedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F39 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.