#1321 [python-blivet] the software raid disk becomes unusable after click "Rescan" twice | rhbz#2236356
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2236356 **
Information from BlockerBugs App:
2236356

Current vote summary

Commented but haven't voted yet: coremodule, frantisekz

The votes have been last counted at 2024-02-27 10:43 UTC and the last processed comment was #comment-898176

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)


I don't like it, but it doesn't read to me like data is lost, and you aren't likely to hit the issue in a "regular" flow, you need to go back and forth once.

BetaBlocker -1

It seems this violates https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria#Custom_partitioning

BetaBlocker +1

The new information in comment 18 makes this feel more blockery to me.

BetaBlocker +1

Discussed during the 2024-02-12 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as it would be helpful to clarify for sure what exactly the status of this issue is with webui/cockpit, webui/blivet and the current UI.

[0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-12/f40-blocker-review.2024-02-12-17.05.txt

BetaFE +1
FinalBlocker +1

Discussed during the 2024-02-19 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as we're still clarifying exactly the status with F40 here. The installer team is also looking at a fix. We have added a needinfo to the bug.

[0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-19/f40-blocker-review.2024-02-19-17.00.log.txt

So I'd say this is kind of a conditional violation of the criteria, the condition being that you use the "re-scan storage" button. But that button is there to be used, and it doesn't seem like an artificial scenario that someone might actually want to use it with an affected RAID array, so:

BetaBlocker +1

It still reads to me like it requires a bit of going back and forth, but in a way commonly encountered. I remain in agreement it's a conditional violation of the custom partitioning criteria.

FinalBlocker +1

AGREED AcceptedBetaBlocker

Discussed during the 2024-02-26 blocker review meeting [1]:

"The installer must be able to detect and install to hardware RAID storage devices."

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-26/f40-blocker-review.2024-02-26-17.01.log.html

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

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

Log in to comment on this ticket.

Metadata