#302 adding gitlab-centos queue and user
Merged 5 years ago by kevin. Opened 5 years ago by lrossett.
fedora-infra/ lrossett/ansible gitlab-centos-mq-setup  into  master

@@ -97,3 +97,23 @@ 

        warning:  1000

        critical: 10000

  

+ # CENTOS GITLAB BEGIN

+ - name: CentOS Gitlab User

+   run_once: true

+   include_role:

+     name: rabbit/user

+   vars:

+      username: gitlab-centos

+ 

+ - name: CentOS Gitlab Queue

+   run_once: true

+   include_role:

+     name: rabbit/queue

+   vars:

+     username: gitlab-centos

+     queue_name: gitlab-centos

+     # TTL: 10 days (in miliseconds)

+     message_ttl: 864000000

+     routing_keys:

+       - "org.fedoraproject.{{ env_suffix }}.gitlab-centos.#"

+ # CENTOS GITLAB END 

\ No newline at end of file

Adds gitlab centos user, queue and routing keys for https://pagure.io/fedora-infrastructure/issue/9417

Changes

  • adds a new user: gitlab-centos;
  • adds a new queue: gitlab-centos binding the following routing key: org.fedoraproject.{{ env_suffix }}.gitlab-centos.#.

Note: I don't have access/perms to run those changes myself.

rebased onto 806b6bf

5 years ago

rebased onto 806b6bf

5 years ago

Pull-Request has been merged by kevin

5 years ago

I've also run the playbook...

Just gave it a try and looks like it worked like a charm :)

Thanks!

I am sending a message to the following topic: org.fedoraproject.prod.gitlab-centos.lrossett.centos-stream-webhooks.push but I can't see it in datagrepper: https://apps.fedoraproject.org/datagrepper/raw?category=gitlab-centos&rows_per_page=1&delta=127800 - is it possible to check if something is missing from the queue/topic config?

Actually it is being sent but I can't see it in datagrepper (consuming messages from fedora-messaging cli works).

Yeah, it was causing our messaging bridge (fedora-messaging -> fedmsg) to crash... so it never made it to datagrepper. ;(

We have patched it to drop messages that are in that format now...

No worries, apologies for the confusion about that :)

We had to delete the queue anyway and create it again with a different routing key, I have filed a new PR for it: https://pagure.io/fedora-infra/ansible/pull-request/308

Metadata