#12725 staging cloud-image-uploader failing to connect with AMQP broker
Closed: Fixed by zlopez. Opened by jcline.

Describe what you would like us to do:


Looks like sometime in the last 24 hours the staging instance of the cloud image uploader began crash looping:

[2025-08-14 14:10:15,575 twisted INFO] Starting factory FedoraMessagingFactoryV2(parameters=<URLParameters host=rabbitmq.stg.fedoraproject.org port=5671 virtual_host=/pubsub ssl=True>, confirms=True)
[2025-08-14 14:10:15,590 fedora_messaging.cli ERROR] The TCP connection appears to have started, but the TLS or AMQP handshake with the broker failed; check your connection and authentication parameters and ensure your user has permission to access the vhost

When do you need this to be done by? (YYYY/MM/DD)


Not urgent, just emails me a lot


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: Needs investigation, low-gain, rabbitmq

Isn't the cert for cloud-image-uploader on staging just expired?

Quite likely that is the issue

Let me check how it could be regenerated.

Metadata Update from @zlopez:
- Issue assigned to zlopez

Checked it out first and it should be valid till Jul 13 2026.

@abompard Isn't this related to the CA changes you did some time ago? https://github.com/fedora-infra/fedora-messaging/issues/440

In any case let me try to regenerate it.

So the new cert is already there, but the cloud-image-uploader is still using the old one.

Here is the PR to fix that https://pagure.io/fedora-infra/ansible/pull-request/2798

Metadata Update from @zlopez:
- Issue untagged with: Needs investigation
- Issue tagged with: low-trouble

And... it's fixed :-)

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

Metadata