fedora-infrastructure

#13018 Pagure Stg is not sending messages
Closed: Fixed with Explanation by kevin. Opened by amedvede.

Closed: Fixed with Explanation
Reopen Issue

Hey all, when I'm creating tickets at stg.pagure.io it seems that it doesn't send any messages, at least I can't see any on https://apps.stg.fedoraproject.org/datagrepper/v2/search?topic=io.pagure.stg.pagure.issue.new. Previously, I had a similar issue https://pagure.io/fedora-infrastructure/issue/12760, but now it's something different. Can you provide me with information on how to troubleshoot this issue? I wanted to see journalctl from pagure-stg02 server, but I believe it requires sysadmin-noc permissions to access the server.

I don't see anything for the entire category on staging:

https://apps.stg.fedoraproject.org/datagrepper/v2/search?category=pagure

...much like your previous ticket ... are you sure it got fixed and was working?
Edited by james

Metadata Update from @james:
- Issue tagged with: low-gain, medium-trouble, pagure, staging

I don't see anything for the entire category on staging:

https://apps.stg.fedoraproject.org/datagrepper/v2/search?category=pagure

...much like your previous ticket ... are you sure it got fixed and was working?

Yeah, after this fix it started to work, I tested it

upd: we have checked and pagure-stg registrate that new message appears but it can't establish connection with rabbitmq01.stg.rdu3.fedoraproject.org we tried nc from pagure-stg02

IIRC pagure-stg isn't fully on the staging env, thus the pagure-stg0X and not pagure0X.stg.

though it looks like in ansible we're setting:

amqp_url = "amqps://pagure.stg:@rabbitmq.stg.fedoraproject.org/%2Fpubsub"

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

Metadata Update from @amedvede:
- Issue assigned to amedvede

Metadata Update from @amedvede:
- Assignee reset

though it looks like in ansible we're setting:
amqp_url = "amqps://pagure.stg:@rabbitmq.stg.fedoraproject.org/%2Fpubsub"

Yeah, Pagure host name looks good, it's the same name that Cerf is telling. The problem is that network of pagure-stg02 isolated or something

ok, this was a rhit firewall issue.

Got them to update that and it seems to be working now:

https://apps.stg.fedoraproject.org/datagrepper/v2/id?id=0b20a10c-571a-4bb1-9144-cbde4555bbcf&is_raw=true&size=extra-large

let me know if I missed anything...

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

It seems to be working, thank you! Can you please let me know what you did to get it working

It was a firewall issue, and not in our firewalls, but in the Red Hat IT firewall. So, we needed to ask them to add a acl to allow pagure-stg01 to be able to talk to rabbitmq.stg.fedoraproject.org (external ip) on the rabbitmq port.

Metadata
None

low-gain medium-trouble pagure staging

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.