Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2266050 ** Information from BlockerBugs App:
Commented but haven't voted yet: coremodule, frantisekz
The votes have been last counted at 2024-03-18 17:58 UTC and the last processed comment was #comment-900919
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
Definitely feels like a violation of the cited system services criteria.
FinalBlocker +1
Discussed during the 2024-03-04 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as it's not clear if a system service is actually failing here (as defined in the criterion and test case), or if this may alternatively be a violation of https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria#SELinux_and_crash_notifications . We'll delay the decision to ask lruzicka for more information.
[0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-04/f40-blocker-review.2024-03-04-17.00.log.txt
I would go with the alternative criterion, as I did not see any crashed services running the command systemctl --failed or systemctl --user --failed. However, the notification is still present in the system, therefore
systemctl --failed
systemctl --user --failed
I have not been able to make any kind of notification pop up across two different composes now (20240306, 20240223). I'm must be not looking in the right place, not following the reproduction steps properly (install on bare metal, reboot), or it's somehow conditional?
AGREED AcceptedFinalBlocker
Discussed during the 2024-03-18 blocker review meeting [1]:
The details of this don't seem to be all nailed down yet, but it definitely seems concerning enough in a couple of ways to accept as a blocker for now: the crash notification may be a violation of the final criterion requiring no crash notifications on first boot if it's confirmed to affect clean installs, and the crash indicates that some configuration migration is failing on upgrades which could cause more serious consequences also.
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-18/f40-blocker-review.2024-03-18-16.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.