Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2308428 ** Information from BlockerBugs App:
Commented but haven't voted yet: frantisekz
The votes have been last counted at 2024-09-30 17:38 UTC and the last processed comment was #comment-936030
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
Again I'll agree with Dusty Mabe's point: "Because of this bug logrotate.service shows up as failed on OSTree based systems. If a fix become available it would be nice to include it as an FE so peoples systems don't have a failing service."
logrotate.service
FinalFE +1
Would be nice to fix a potential failing service after upgrade.
AGREED AcceptedFinalFE
Discussed during the 2024-09-30 blocker review meeting [1]:
This can cause problems for atomic installs on rebase from 40 to 41, so if the fix doesn't make it before freeze, we should take it to avoid problems for users who rebase during the freeze.
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-09-30/f41-blocker-review.2024-09-30-16.00.log.html
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F41 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.