I would like to have a staging fedora-messaging publishing access to be used in the mbbox operator, I think it needs both certs and a mq key for that.
It needs publishing access because koji-hub pushes messages on several build stages.
the sooner the merrier ;)
So, to clarify here... this is for mbbox running in a/some CentOS openshift to allow it to connect to/publish to the fedora-messaging bus?
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Reporter (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
yes, correct.
it currently needs staging access since it is on development phase.
Metadata Update from @pingou: - Issue assigned to pingou
@lrossett I have create the certificates, how can I give them to you?
I've sent the certs to @lrossett yesterday who acked on IRC receiving them.
Let us know if you need anything else! :)
Metadata Update from @pingou: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Could you please send me the topic format I should be using? I tried to use something like "org.fedoraproject.stg.mbbox-centos.message" but I get the following error: Unable to connect to the message broker: Publishing timed out after waiting 30 seconds.
There is no restriction on the topic, the one you've used follow our standards (org.{fedoraproject,centos}.{stg,prod}.<servicename>.<rest of the topic>). So this error is more likely something else.
org.{fedoraproject,centos}.{stg,prod}.<servicename>.<rest of the topic>
what about the exchange name?
https://pagure.io/fedora-infra/ansible/blob/master/f/roles/openshift-apps/toddlers/templates/fedora-messaging.toml says amq.topic
amq.topic
Enabling debug logging shows this message:
2020-10-27 14:36:13,529 - [DEBUG fedora_messaging.api] Canceled publish of Message(id='273ed91d-b8b5-487a-9576-95b9fbdf3eec', topic='org.fedoraproject.stg.centos-mbbox.test', body={'test_key1': 'test_value1'}) to amq.topic due to timeout
is the port the correct one (5671)? I tried to telnet to it but it didn't work while the 443 one did.
Login to comment on this ticket.