#9061 no queue 'osci-pipelines-queue-4' in vhost '/pubsub'
Closed: Fixed 3 years ago by astepano. Opened 3 years ago by astepano.

Hello, there was an ticket to add new queues:

https://pagure.io/fedora-infrastructure/issue/8996

PR: https://pagure.io/fedora-infra/ansible/pull-request/118 was merged,
We can connect to the RabbitMQ.

But receive next reply:

2020-06-22 13:49:12.179+0000 [id=200]   INFO    c.r.j.p.c.m.RabbitMQMessagingWorker#subscribe: Subscribing job 'RabbitMQ_Copr_Heartbeat' to org.fedoraproject.prod.copr.build.start topic.
2020-06-22 13:49:12.184+0000 [id=200]   SEVERE  c.r.j.p.c.m.RabbitMQMessagingWorker#subscribe: Eexception raised while subscribing job 'RabbitMQ_Copr_Heartbeat', retrying in 1 minutes.
com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=404, reply-text=NOT_FOUND - no queue 'osci-pipelines-queue-4' in vhost '/pubsub', class-id=50, method-id=20)
    at com.rabbitmq.client.impl.ChannelN.asyncShutdown(ChannelN.java:522)
    at com.rabbitmq.client.impl.ChannelN.processAsync(ChannelN.java:346)
    at com.rabbitmq.client.impl.AMQChannel.handleCompleteInboundCommand(AMQChannel.java:182)
    at com.rabbitmq.client.impl.AMQChannel.handleFrame(AMQChannel.java:114)
    at com.rabbitmq.client.impl.AMQConnection.readFrame(AMQConnection.java:672)
    at com.rabbitmq.client.impl.AMQConnection.access$300(AMQConnection.java:48)
    at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:599)
    at java.lang.Thread.run(Thread.java:748)
Caused: com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=404, reply-text=NOT_FOUND - no queue 'osci-pipelines-queue-4' in vhost '/pubsub', class-id=50, method-id=20)

Pleas help. Thank you!


Tagging @kevin and @abompard (Please let me know if tagging is an appropriate action)

From : https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/rabbitmq.html

/pubsub
The /pubsub virtual host is the generic publish-subscribe virtual host used by most applications. Messages published via AMQP are sent to the “amq.topic” exchange. Messages being bridged from fedmsg into AMQP are sent via “zmq.topic”.

Seems our side is OK. Maybe something wrong with my merged PR: https://pagure.io/fedora-infra/ansible/pull-request/118 ?

So, yes, it was the PR. ;(

first, I didn't notice that it failed when I ran the playbook after merging. This is because we have 3 rabbitmq servers in our cluster and those ansible tasks are run_once. Thats fine, but when it failed on that task (making those queues in a loop), it just failed rabbitmq01 out, the next task just ran on rabbitmq02 and went on. The playbook finished fine. So, I think we need to perhaps add something there to fail the entire playbook if those fail. Or I just need to pay attention more. ;(

The second issue (causing the task to fail) was that you were using a loop, which by default uses 'item' in ansible. Unfortunately, the rabbit/queue rule also uses 'item' and they clash. ;( So, I moved the call in apps.yml to use a different variable.

The playbook has now run and completed and created those queues. Can you confirm you can reach them now and close this when it's working for you?

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

3 years ago

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

3 years ago

Login to comment on this ticket.

Metadata