This definitely feels like a "sane" thing to do, so the footnote in the cited criteria applies.

FinalBlocker +1

I guess this depends on whether we want to go with the exact wording of the criterion, or with the expected behavior. For me, the expected behavior is that any partition can be reformatted (to the same or a different filesystem). But the exact wording is that it only has to work if anaconda offers the functionality in the first place.

Another way to look at this is that this is a violation of "Assign mount points to existing storage volumes" from here, in a particular case where you want to assign the / mount point to an existing btrfs partition (you can't do that because anaconda doesn't let you to reformat it, which is a requirement for the / mount point assignment).

Discussed during the 2023-08-28 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as this is a complex area and we're really not too sure how to handle this. It's an awkward experience but it is possible to work with it, and we don't know how practical it is to 'fix' this on the development side. We'll delay the decision and ask anaconda/blivet devs to provide input on that part.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-08-28/f39-blocker-review.2023-08-28-16.07.txt

I talked to @vtrefny last week about this. I hoped he would've posted his thoughts in Bugzilla, but so far he hadn't, so I'll summarize myself. It's not clear whether the fix would be simple or complex. It's something Vojtěch would like to fix eventually, but the current priorities are elsewhere (webUI). The installer had behaved this way for many releases, and our release criteria only suggest it has to work when it's offered (and this is not offered). Last but not least, Blivet-GUI integration in Anaconda is probably going away next release or so (just the integration, the standalone app will stay), and Cockpit partitioning might be used instead. Combining all these pieces together, it probably doesn't make a lot of sense to push Anaconda devs to fix this asap and make it a blocker.

AGREED RejectedFinalBlocker

Discussed during the 2023-09-04 blocker review meeting [1]:

based on feedback from vtrefny via kparal at https://pagure.io/fedora-qa/blocker-review/issue/1157#comment-872594 , we agree it doesn't make sense to take too strict of an interpretation and make this a blocker. we will document how to handle it as a common bug.

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2023-09-04/f39-blocker-review.2023-09-04-16.00.log.txt

The following votes have been closed:

• Rejected FinalBlocker (+1, 0, -0)
  • +1 by nielsenb

Release F39 is no longer tracked by BlockerBugs, closing this ticket.