infra/tickets

dist-git lookaside uploads fedora-messaging not functioning #13380

New issue

Closed

opened 2026-06-01 18:27:04 +00:00 by kevin · 0 comments

kevin commented

2026-06-01 18:27:04 +00:00

Owner

Description of request

In looking at something else, I noticed that the fedora-messages that are supposed to be emitted on lookaside uploads was not working. I fixed several issues, but it's hit a new one after that I am not sure on.

We had mistakenly been putting the tls cert req into the file that was supposed to be the CA, so it was failing on that.
We didn't allow apache permission to access the key to be able to auth
The following traceback now happens:

 --- <exception caught here> ---: /var/www/bin/suexec-upload.sh
   File "/usr/lib/python3.6/site-packages/fedora_messaging/api.py", line 262, in _twisted_publish: /var/www/bin/suexec-upload.sh
     yield _twisted_service._service.factory.publish(message, exchange=exchange): /var/www/bin/suexec-upload.sh
   File "/usr/lib/python3.6/site-packages/fedora_messaging/twisted/factory.py", line 238, in publish: /var/www/bin/suexec-upload.sh
     protocol = yield self.when_connected(): /var/www/bin/suexec-upload.sh
   File "/usr/lib/python3.6/site-packages/fedora_messaging/twisted/factory.py", line 203, in when_connected: /var/www/bin/suexec-upload.sh
deferred: /var/www/bin/suexec-upload.sh
 fedora_messaging.exceptions.ConnectionException: : /var/www/bin/suexec-upload.sh: /var/www/bin/suexec-upload.sh
 Error sending message 8a5bdbe8-7e27-4973-ac7f-7c1d54da7ca4: : /var/www/bin/suexec-upload.sh

I think this might be because we never add a 'git-hooks' rabbitmq user. However, I can't seem to find where we ever did that in the past either, so not sure if thats the issue or it's a rhel8 fedora-messaging problem or what.

Perhaps @abompard might be able to look?

### Description of request In looking at something else, I noticed that the fedora-messages that are supposed to be emitted on lookaside uploads was not working. I fixed several issues, but it's hit a new one after that I am not sure on. 1. We had mistakenly been putting the tls cert req into the file that was supposed to be the CA, so it was failing on that. 2. We didn't allow apache permission to access the key to be able to auth 3. The following traceback now happens: ``` --- <exception caught here> ---: /var/www/bin/suexec-upload.sh File "/usr/lib/python3.6/site-packages/fedora_messaging/api.py", line 262, in _twisted_publish: /var/www/bin/suexec-upload.sh yield _twisted_service._service.factory.publish(message, exchange=exchange): /var/www/bin/suexec-upload.sh File "/usr/lib/python3.6/site-packages/fedora_messaging/twisted/factory.py", line 238, in publish: /var/www/bin/suexec-upload.sh protocol = yield self.when_connected(): /var/www/bin/suexec-upload.sh File "/usr/lib/python3.6/site-packages/fedora_messaging/twisted/factory.py", line 203, in when_connected: /var/www/bin/suexec-upload.sh deferred: /var/www/bin/suexec-upload.sh fedora_messaging.exceptions.ConnectionException: : /var/www/bin/suexec-upload.sh: /var/www/bin/suexec-upload.sh Error sending message 8a5bdbe8-7e27-4973-ac7f-7c1d54da7ca4: : /var/www/bin/suexec-upload.sh ``` I think this might be because we never add a 'git-hooks' rabbitmq user. However, I can't seem to find where we ever did that in the past either, so not sure if thats the issue or it's a rhel8 fedora-messaging problem or what. Perhaps @abompard might be able to look?

smoliicek added the

labels

2026-06-01 19:05:50 +00:00

abompard referenced this issue from a commit

2026-06-02 09:55:14 +00:00

Add the RabbitMQ user for the lookaside cache

abompard closed this issue

2026-06-02 09:55:14 +00:00

abompard self-assigned this

2026-06-02 10:00:01 +00:00

Sign in to join this conversation.

No labels

forgejo_migration

Needs investigation

packager_workflow_blocker

🔥 URGENT 🔥

Waiting on Assignee

Waiting on External

Waiting on Reporter

release-monitoring

request-for-resources

websites-general

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

infra/tickets#13380

No description provided.