The AMQP URI for resultsdb was changed recently.
I assume this change was for the ci instance of resultsdb but tcp connections between resultsdb01.qa.fedoraproject.org and rabbitmq.fedoraproject.org time out.
I've downgraded python3-pika and changed the AMQP uri back to rabbitmq01.phx2.fedoraproject.org for now so that messages continue to be emitted but this is just a band-aid
Tagging @pingou as it was his ansible change and he may know more about what needs to fixed between resultsdb01.qa and rabbitmq.fedoraproject.org to allow for connections
Is there any update to this? Thanks.
This is a RHIT firewall port that will need to be opened, as it wasn't requested previously.
Is there a different process we need to kick off to make that happen?
No, we just need about 10 more sysadmins dealing with tickets. :)
In any case, I am not sure we do need ports open. Currently it's getting external IP's for rabbitmq.fedoraproject.org, so it should be going in via the outside, and those ports are supposedly already open.
We could need to point it to internal IP's and open those ports from its IP or the qa network, but I would think the current setup would work.
Internal ticket is in.
ok, this should be set. Please test!
Metadata Update from @smooge: - Issue assigned to kevin - Issue priority set to: Waiting on Reporter (was: Needs Review)
I've updated resultsdb-stg and resultsdb-prod and everything appears to be working. Thanks for getting this taken care of
Metadata Update from @tflink: - Issue close_status updated to: Fixed - Issue priority set to: Needs Review (was: Waiting on Reporter) - Issue status updated to: Closed (was: Open)