copr-be-dev fails to post to fedora-messaging bus

[praiskup]

[2025-01-07 07:14:12,365][ INFO][PID:234943] Sending fedora-messaging bus message in build.start
[2025-01-07 07:14:43,122][ ERROR][PID:234943] Attempt 1 to publish a message failed (in /usr/lib/python3.13/site-packages/fedora_messaging/api.py:321)
[2025-01-07 07:15:13,130][ ERROR][PID:234943] Attempt 2 to publish a message failed (in /usr/lib/python3.13/site-packages/fedora_messaging/api.py:321)

[praiskup]

Work-around is to drop the message-bus config.

[nikromen]

it basically works (see https://apps.stg.fedoraproject.org/datagrepper/raw?category=copr&delta=172800)... it's just the staging instance of the messaging broker is sometimes unstable (rabbitmq.stg.fedoraproject.org sometimes timeouts...). I don't think we can do something about this on our side

[nikromen]

So last week I tried to connect to stg messaging broker instance and sometimes got timeouts (I tried this on copr-prod and copr-stg to eliminate the possibility of badly configured copr-stg and got timeouts on both). However prod messaging broker instance connected (with certificate error of course) successfully, so this is problem-related at the end of fedora messaging broker. The script I used is this:

import pika

url_a = "amqps://copr.stg:@rabbitmq.stg.fedoraproject.org/%2Fpubsub"
params = pika.URLParameters(url)
connection = pika.BlockingConnection(params)

that's how fedora-messaging connects to the broker, very simplified

Also, telnet sometimes failed too...

telnet rabbitmq.stg.fedoraproject.org 5671

But right now staging messaging broker works almost in 100% cases so I gues the staging instance is just sometimes unstable...

[nikromen]

AI: create ticket in fedora infra