#10284 coreos-koji-tagger stopped processing events (fedmsg)
Closed: Fixed 2 years ago by dustymabe. Opened 2 years ago by dustymabe.

  • Describe the issue

Our coreos-koji-tagger stopped processing events. We're not sure where the problem is. It watches the org.fedoraproject.prod.github.push messages. The tagger is defined here and the fedmsg.toml is configured in the Dockerfile

  • When do you need this? (YYYY/MM/DD)

Today would be nice, but within the next 5 business days, would be acceptable.

  • When is this no longer needed or useful? (YYYY/MM/DD)

N/A

  • If we cannot complete your request, what is the impact?

We no longer auto tag in packages into coreos-pool when the upstream git repo is changed.


Can someone check the queue to see if it's got a lot of messsages in it?

Metadata Update from @kevin:
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

What is the name of the queue?

Does this answer the question?

[queues.ffe0f5d3-b5b1-4a77-ad47-6ba563ebeec5]
durable = false
auto_delete = true
exclusive = true
arguments = {}

[[bindings]]
queue = "ffe0f5d3-b5b1-4a77-ad47-6ba563ebeec5"
exchange = "amq.topic"
routing_keys = ["org.fedoraproject.prod.github.push"]

Yes. There's 0 messages in that queue.

hmm. any other ideas why coreos-koji-tagger stopped processing messages?

https://os.fedoraproject.org/console/project/coreos-koji-tagger/browse/pods/coreos-koji-tagger-21-7rqjf?tab=logs

We should be seeing Skipping message from unrelated repo messages often if it was processing thing.

basically all it does now is an initial run on first startup (i.e. no need for fedmsg) and then nothing after that (should be processing messages).

ok so I'm removing my application from the equation and just using fedora-messaging. Running the following I don't see messages getting printed out, but if I follow datagrepper I can see them coming in...

fedora-messaging --conf=/etc/fedora-messaging/fedora.toml consume --callback=fedora_messaging.example:printer --routing-key org.fedoraproject.prod.github.push

Who can help me figure this out?

CC: @abompard or @jcline if he's bored/has some time. ;)

I don't have access to those logs so I can't begin to speculate. It looks like that's the public broker, maybe the federation between the two is broken.

Checked in after kevin messaged me:

11:03:20          nirik | dustymabe: abompard fixed a bridge issue... try your fedora-messaging thing again, hopefully that was
                        | related and now will work.

Things are working again

Metadata Update from @dustymabe:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog