automatic bodhi update creation for rawhide and ELN not working since July 13 ~23:00 UTC #13461
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#13461
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of request
It looks like the automatic update creation for rawhide and ELN builds isn't working. The last build that got tagged into f45 by bodhi was:
(from
koji list-history --tag f45 --after="2026-07-13 23:00" | grep bodhi)There is a growing backlog of builds tagged f45-updates-candidate and eln-updates-candidate that aren't getting picked up.
I think i see the problem and have fixed it, but will see/watch.
So, the issue was that the bodhi consumer pod had stopped... consuming.
Likely due to the reinstall of the vmhost yesterday that had rabbitmq01 on it. We need to disentangle things so rabbitmq01 being down doesn't cause all the consumers to have problems. ;(
In any case a:
oc rollout restart deploy bodhi-consumer -n bodhi
restarted the pod and it consumed all the back messages.
I guess CI is churning through the backlog now.
I think it's mostly processed everything, there's a few more still in ci...
Please re-open if you see any further issues.
Seems stuck again:
Looking into it
it is not the bodhi pod, checking bodhi logs
caught it, should be fixing now
(edit: it didnt work)
Actually sorry - I only looked at the number of builds earlier: it seems all those 43 builds were from late May...
It looks like this is fixed now.
Correct!
But some strange untags seemed to happen to some of those packages in early June by
oscar.I might still be good to cleanup the rest of
f45-updates-testing-pendingperhaps.oscar is the user that does koji-gc: https://fedoraproject.org/wiki/Koji/GarbageCollection
so its normal that old builds that aren't in releases are untagged by it.