Please correct me if my expectation is incorrect but I think when a new ticket or a comment is created in the STG Bugzilla instance https://bugzilla.stage.redhat.com
A message should be sent to the STG fedora-messaging bus and should for example appear in the STG datagrepper https://apps.stg.fedoraproject.org/datagrepper/v2/search?rows_per_page=1
This doesn't happen now (and if I remember correctly, it did in the past).
This is a problem for me because I rely on this during Fedora Review Service development, and currently two pull requests are waiting to be tested and merged.
Can you please make it work? I don't really care about the datagrepper part, I use this config https://github.com/FrostyX/fedora-review-service/blob/main/conf/fedora.stg.toml and i want to receive the messages, that's all.
At your convenience
I checked the bugzilla2fedmsg deployment on staging and it seems to have same issues as the production version that it stops sending messages after some time. I restarted it and the messages are being sent again.
Thanks for letting as know. It should be OK now.
Metadata Update from @zlopez: - Issue assigned to zlopez - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @zlopez: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
and the messages are being sent again.
I don't want to be a party pooper but I don't think they are. Maybe it already broke again?
seems to have same issues as the production version that it stops sending messages after some time.
By the way we merged a PR with some improvement logging. Maybe there will be something in the logs now? https://github.com/fedora-infra/bugzilla2fedmsg/pull/25
You are right, I was looking at bad datagrepper filter. Let me push the changes to staging branch and I will deploy a new build in staging.
Metadata Update from @zlopez: - Issue status updated to: Open (was: Closed)
So I deployed the latest version and tried to create a test comment. It doesn't seem the message even arrived to bugzilla2fedmsg on staging. There is only the heartbeat message in logs.
I'm wondering if the URI configured for the staging is actually correct uri = "ssl://umb.stage.api.redhat.com:61612". I would assume it should be ssl://umb.api.stage.redhat.com:61612, but I'm not sure how to even test if something with ssl:// is accessible.
uri = "ssl://umb.stage.api.redhat.com:61612"
ssl://umb.api.stage.redhat.com:61612
ssl://
According to internal docs that url is right.
Can we tell if it's connecting / authenticating ok?
It's hard to tell from the logs as I don't see anything arriving through it.
This is all I can see in the logs:
2024-07-15 11:12:53,696 [bugzilla2fedmsg.consumer DEBUG] Initialized bz2fm STOMP consumer. 2024-07-15 11:12:53,696 [bugzilla2fedmsg.consumer DEBUG] STOMP consumer is connecting... 2024-07-15 11:12:53,824 [bugzilla2fedmsg.consumer INFO] STOMP consumer is ready
Metadata Update from @zlopez: - Assignee reset
I don't currently have time to work on this. If anybody wants to investigate this, feel free to assign yourself to this ticket.
This could well be a problem with our connection to the staging message bus internally. So, I suspect the next thing to try might be an internal redhat ticket asking if the bus is ok and if they can see us connecting to it.
So, you said somewhere that I can't find that this is working again? Or no?
That is already fixed, the problem was on the Red Hat side, they already fixed it.
Closing this as fixed.
Log in to comment on this ticket.