Follow-ups to #12807 and #12808, apparently those are not the only dead queues. These are under the repos in https://github.com/fedora-ci?q=-trigger and each branch under it. We should revise them and nuke the now dead ones. The question in #12807 stands though, in which order should we do this?
If you can stop the consumers reading from these queues, I can delete them from the server afterwards. Actually I can delete them anytime but that may crash your consumers.
Currently, this is the status: - 1 consumer connected: 4, 6, 7, 10, 11, 12, 14, 15 - no consumer connected: 0, 1, 2, 5, 9, 16
Metadata Update from @abompard: - Issue assigned to abompard
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
Metadata Update from @abompard: - Issue tagged with: rabbitmq
Ok, let me try to breakdown the list:
Keep: 4, 7, 10, 11, 15, 15 Delete: 0, 1, 6, 12, 13 Unaccounted for: 2, 5, 9, 16
Others:
That should cover all fedora-ci/*-trigger repos and their branches
fedora-ci/*-trigger
6 and 13 are gone now.
I've deleted 0 and 1, but 12 still has a consumer connected. Should I delete it nonetheless? It will very probably crash this consumer.
12 does? I didn't see it in the fedora-cirepo and the only reference I found was in a disabled job https://osci-jenkins-1.ci.fedoraproject.org/job/eln-build-trigger/. Could maybe try to get a response from @msrb to see if this is hidden somewhere else?
fedora-ci
12 does?
Yeah, it's currently receiving messages in the org.fedoraproject.prod.buildsys.tag topic.
org.fedoraproject.prod.buildsys.tag
Well that matches with https://github.com/fedora-ci/eln-build-trigger/blob/master/Jenkinsfile. Maybe the jenkins did not properly disable it? Will wait for Michal's feedback on that for a while, otherwise I could try to explicitly delete that job and see if that changes anything.
I still see a consumer on 12. ;(
I went ahead and nuked that job
and the queue is gone too.
I think with that this is all done? Or was there anything we missed?
Jenkins is such a mystey yeqh all done for this issue
Metadata Update from @lecris: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.