Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2012758 Information from BlockerBugs App: <img alt="2012758" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2012758" />
Commented but haven't voted yet: adamwill, bcotton, mattdm, lruzicka, coremodule
The votes have been last counted at 2021-10-20 22:54 UTC and the last processed comment was #comment-758529
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
Can anyone please point out the criteria for this as a blocker?
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Automatic_partition_decryption_.28Clevis.29 would be the criterion, but I'm waiting for @pbrobinson to clarify whether the issue actually affects F35...
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Automatic_partition_decryption_.28Clevis.29 would be the criterion, but I'm waiting for pbrobinson to clarify whether the issue actually affects F35...
FWIW, the original report seems to indicate F35
FinalBlocker +1
ok then FinalBlocker +1
IoT is an edition and its flagship features should work.
AGREED AcceptedFinalBlocker
Discussed during the 2021-10-18 blocker review meeting: [0]
The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:
"When configured on hardware with a Trusted Platform Module (TPM), it must be possible for the Clevis utility to automatically decrypt any encrypted partitions on boot without any user intervention".
If further information suggests this is not the case, we may change the decision.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-18/f35-blocker-review.2021-10-18-16.00.txt
The following votes have been closed:
We got some news at this ticket in Bugzilla. So if this is the case, and is confirmed, I vote for waive the blocker status. What do you think?
Per discussion in the bug, I think we should revote this.
REVOTE FinalBlocker
FinalBlocker -1 FinalFE -1
I think it's been established in the BZ that it's due to a misconfiguration and should not cause problems on properly-configured setups. I'm voting -1 on FE because I worry that any attempt to fix this crash so late would introduce unnecessary risks.
AGREED RejectedFinalBlocker RejectedFinalFE
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F35 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.