Our pipelines are still triggering on FedMsg, let's switch to FedoraMessaging.
We have got some queues that we can use to trigger, so PR to fix trigger was done on https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/pull/228
unfortunately, it looks like our Jenkins doesn't have the provider configured properly
Eexception raised while subscribing job 'fedora-task-pipeline-trigger', retrying in 1 minutes. com.rabbitmq.client.ShutdownSignalException: channel error; protocol method: #method<channel.close>(reply-code=403, reply-text=ACCESS_REFUSED - access to queue 'osci-pipelines-queue-10' in vhost '/pubsub' refused for user 'centos-ci', 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.base/java.lang.Thread.run(Thread.java:834)
Change got reverted
https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/pull/229
This will not work.
queue 'osci-pipelines-queue-10' in vhost '/pubsub' refused for user 'centos-ci'
I will add the new access to FedoraMessaging (rabbitmq) a in a few days. Until than please use workaround you have now.
Update. New issue popped - up. I opened issue to track: https://pagure.io/fedora-infrastructure/issue/9061
Access to RabbitMQ was deployed to 2x Jenkinses .
Example of running jobs:
Queues numbers 4,5 are used.
Please track used queues at: https://pagure.io/fork/astepano/fedora-ci/docs/blob/master/f/modules/ROOT/pages/jenkins.adoc
Initial PR was with table:
https://pagure.io/fedora-ci/docs/pull-request/42
I cannot edit the ticket metadata. The ticket can be closed.
Metadata Update from @bgoncalv: - Issue status updated to: Closed (was: Open)