For example the message below was published to fedmsg-stage, but we can't find it on datagrepper.
{"msg":{"branch":"master","build_id":"21","build_url":"https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-stage-build-trigger/detail/fedora-stage-build-trigger/21/pipeline/","ci_topic":"org.centos.stage.ci.pipeline.allpackages-build.package.queued","comment_id":null,"namespace":null,"nvr":"","original_spec_nvr":"","ref":"x86_64","repo":"fedora-gather-easyfix","rev":"kojitask-90008863","scratch":false,"status":"SUCCESS","test_guidance":"''","username":"pingou"},"msg_id":"2019-dcbc7417-c91a-424a-aded-8ae66f6d0466","timestamp":0,"topic":"org.centos.stage.ci.pipeline.allpackages-build.package.queued"}
https://apps.stg.fedoraproject.org/datagrepper/id?id=2019-dcbc7417-c91a-424a-aded-8ae66f6d0466&chrome=false&is_raw=false
It might be the same issue as https://pagure.io/fedora-infrastructure/issue/7793
I don't know if it is related or not, but message published to prod fedmsg also shows on stage datagrepper...
https://apps.fedoraproject.org/datagrepper/id?id=2019-c1392ae8-1c82-429d-8971-0e67140d1390&is_raw=true&size=extra-large
https://apps.stg.fedoraproject.org/datagrepper/id?id=2019-c1392ae8-1c82-429d-8971-0e67140d1390&is_raw=true&size=extra-large
So there are a couple of things here:
IIRC there is a bridge in ci.centos.org that signs and relay messages sent by the pipeline, so, is the right bridge used? Is it working as expected?
On our side, we should check if ci.centos.org is allowed to send org.centos.stg (or is it .stage?) messages.
@bstinson @siddharthvipul1 could you check the first point?
@bgoncalv which topics exactly are you sending in stg?
@pingou it is basically the same topics we send on prod, just replace the org.centos.prod prefix by org.centos.stage.
org.centos.prod
org.centos.stage
The relay was stuck again.
It's really difficult for us to monitor for this, because the process stays alive but stops passing messages.
Is there anything further to do here? Should we just close this out?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
I see the message appearing on stage datagrepper, so I think it can be closed.
Metadata Update from @mizdebsk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.