BetaBlocker -1
BetaFE -1

There's no specific criterion I can find that this violates, so I don't think this warrants being a blocker. However, the subsystems that it touches are so important that I also would not want to accept a change after the Freeze date (2022-02-22), for fear of causing more problems.

I don't see any specific TPM criteria. Maybe we should have one?

BetaBlocker -1

BetaBlocker -1
FinalBlocker +1

This appears to violate the Automatic partition decrpytion criterion, but that's a Final criterion. I don't see anything applicable in Basic or Beta.

AGREED RejectedBetaBlocker
AGREED AcceptedBetaFE

Discussed during the 2022-02-07 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker (Beta)" and an "AcceptedFreezeException (Beta)" was made as this does not appear to violate any Beta criteria, but it is useful functionality and would be a showstopper for anyone using it on F35 who upgrades to F36, so accepted as an FE issue.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-07/f36-blocker-review.2022-02-07-17.00.txt

The following votes have been closed:

• Rejected BetaBlocker (+0, 0, -3)
  • -1 by sgallagh, nielsenb, bcotton
• Accepted BetaFreezeException (+0, 0, -1)
  • -1 by sgallagh

There's no specific criterion I can find that this violates, so I don't think this warrants being a blocker. However, the subsystems that it touches are so important that I also would not want to accept a change after the Freeze date (2022-02-22), for fear of causing more problems.

It would stop IoT edition with an encrypted hard disk from booting to userspace if the key is stored in a TPM, does non booting count as a blocker?

There's no specific criterion I can find that this violates, so I don't think this warrants being a blocker. However, the subsystems that it touches are so important that I also would not want to accept a change after the Freeze date (2022-02-22), for fear of causing more problems.

It would stop IoT edition with an encrypted hard disk from booting to userspace if the key is stored in a TPM, does non booting count as a blocker?

As noted above, that's a Final criterion, not Beta. I'm absolutely in favor of calling this a Final blocker.

There's no specific criterion I can find that this violates, so I don't think this warrants being a blocker. However, the subsystems that it touches are so important that I also would not want to accept a change after the Freeze date (2022-02-22), for fear of causing more problems.

It would stop IoT edition with an encrypted hard disk from booting to userspace if the key is stored in a TPM, does non booting count as a blocker?

As noted above, that's a Final criterion, not Beta. I'm absolutely in favor of calling this a Final blocker.

I think it should be Beta, an unusable system should block at all points

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