Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2396334 ** Information from BlockerBugs App:
Commented but haven't voted yet: geraldosimiao
The votes have been last counted at 2025-09-22 16:10 UTC and the last processed comment was #comment-986794
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
This seems weird, I'll try to reproduce this.
Seems weird, don't think I would block a release on it.
FinalBlocker -1
The updates-testing repo isn't enabled by default and vast majority of users will not use this repo (speculation) and doesn't seem to effect the update progress for the rest of the system therefore...
I would certainly block on this, if it was a general issue. But I don't think it is, I certainly can't reproduce it, haven't seen any other reports like this, and it feels like just some local mirror sending corrupt data. For the moment:
I have not seen it either.
Yeah haven't seen this.
yeah, I'm with kparal on this. probably a mirror issue. FinalBlocker -1 AGREED RejectedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F43 is no longer tracked by BlockerBugs, closing this ticket.