#8235 Unable to create RabbitMQ queue
Closed: Fixed 4 years ago by kevin. Opened 4 years ago by mizdebsk.

Ansible rabbit/queue role fails to create queue in production with the following error:

TASK [rabbit/queue : Create the koschei queue in RabbitMQ] ****************************************************************************************************
Monday 23 September 2019  15:38:29 +0000 (0:00:06.834)       0:00:07.281 ****** 
fatal: [os-master01.phx2.fedoraproject.org -> rabbitmq01.phx2.fedoraproject.org]: FAILED! => {"changed": false, "details": "{\"error\":\"not_authorised\",\"reason\":\"User not authorised to access virtual host\"}", "msg": "Invalid response from RESTAPI when trying to check if queue exists"}

Reproducible with ansible-playbook /srv/web/infra/ansible/playbooks/openshift-apps/koschei.yml -l \!staging


Metadata Update from @mizdebsk:
- Issue marked as blocking: #8205

4 years ago

ok. I think I have fixed this by changing the admin permissions setup in the cluster playbook.

:rabbit:

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

4 years ago

This error is still reproducible.

Metadata Update from @mizdebsk:
- Issue status updated to: Open (was: Closed)

4 years ago

Metadata Update from @mizdebsk:
- Issue unmarked as blocking: #8205

4 years ago

Previously as a workaround I used to run playbooks/groups/rabbitmq.yml, however now even this playbook fails with the same error:

TASK [rabbitmq_cluster : Create the zmq.topic exchange in /public_pubsub] *************************************************************************************
Tuesday 24 September 2019  10:28:45 +0000 (0:00:00.617)       0:03:20.814 ***** 
fatal: [rabbitmq01.phx2.fedoraproject.org -> rabbitmq01.phx2.fedoraproject.org]: FAILED! => {"changed": false, "details": "{\"error\":\"not_authorised\",\"reason\":\"User not authorised to access virtual host\"}", "msg": "Invalid response from RESTAPI when trying to check if exchange exists"}

@abompard fixed this up today! Kudos!

It was actually the odcs playbook setting up it's own admin user perms and interfering with the main one. Also openqa-stg has an issue trying to setup a queue in prod using the staging rabbitmq admin password.

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

4 years ago

Actually the openqa-stg thing is fine, I was wrong on that one.

Login to comment on this ticket.

Metadata