#871 [greenboot] greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." | rhbz#2121944
Closed 3 months ago by blockerbot. Opened 6 months ago by blockerbot.

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

Current vote summary

  • Accepted FinalBlocker (+1, 0, -0)
  • Accepted BetaFreezeException (+0, 0, -0)

Commented but haven't voted yet: coremodule, gui1ty

The votes have been last counted at 2022-08-31 17:03 UTC and the last processed comment was #comment-814559

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)


AGREED AcceptedBetaFE
AGREED AcceptedFinalBlocker

Discussed during the 2022-08-29 blocker review meeting: [0]

The decision to classify this bug as both an "AcceptedBlocker (Final)" and an "AcceptedFreezeException (Beta)" was made as this is a clear violation of IoT criterion "The Greenboot service must be present on all images and installed by default when using the ISO installer. The service must be enabled to run on boot and function as intended" and the generic "all services must start successfully" criterion. It is also accepted as a Beta FE as it's a significant issue we would like to be fixed.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-08-29/f37-blocker-review.2022-08-29-16.01.txt

The following votes have been closed:

  • Accepted FinalBlocker (+1, 0, -0)
  • Accepted BetaFreezeException (+0, 0, -0)

BetaFE +1 FinalBlocker +1

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

3 months ago

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

Login to comment on this ticket.

Metadata