NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
I would like to reserve a fedora-messaging queue identifier for the DistroBuildSync tool so that if it crashes and remains down for an extended period, we can still resume the automatic builds. This instance of DistroBuildSync will be used to build CentOS Stream 10 packages from successful ELN builds.
Please create a user distrobuildsync-cs and the associated certificates and keytab as was done for #10200.
distrobuildsync-cs
routing_keys = ["#.buildsys.repo.done", "#.buildsys.tag"]
2023-05-19
Correction, we need:
routing_keys = ["#.buildsys.repo.init", "#.buildsys.repo.done", "#.buildsys.tag"]
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
I'm seeing plenty of messages in distrobuildsync-eln queue. Is this related to this request?
distrobuildsync-eln
Not directly related, but similar functionality. The distrobuildsync-eln queue is used to monitor Rawhide builds and trigger ELN builds.
The new queue will be used to monitor ELN tagging events and trigger git-sync and builds in CentOS Stream 10.
Metadata Update from @kevin: - Issue assigned to kevin
ok. done.
I created rabbitmq/fedora-messaging certs in ansible-private and put the cert/key in your homedir on batcave01
I created a keytab on ipa01 for the service and put it in your homedir on batcave01.
I added the app to the rabbitmq cluster playbook and ran it, so the queue should be there now.
Let us know if you need anything else.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.