#7793 CI message sent to stage fedmsg doesn't show on stage datagrepper
Closed: Fixed 4 months ago by bgoncalv. Opened 4 months ago by bgoncalv.

snip from https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-rawhide-stage-pr-pipeline/356/consoleText

[2019-05-13T22:57:50.462Z] Topic is org.centos.stage.ci.pipeline.allpackages-pr.package.running
[Pipeline] readJSON
[Pipeline] retry
[Pipeline] {
[Pipeline] timeout
[2019-05-13T22:57:50.587Z] Timeout set to expire in 1 min 0 sec
[Pipeline] {
[Pipeline] sendCIMessage
[2019-05-13T22:57:50.624Z] Sending message for job 'fedora-rawhide-stage-pr-pipeline'.
[2019-05-13T22:57:55.629Z] JSON message body:
[2019-05-13T22:57:55.629Z] {"msg":{"branch":"master","build_id":"356","build_url":"https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-rawhide-stage-pr-pipeline/detail/fedora-rawhide-stage-pr-pipeline/356/pipeline/","ci_topic":"org.centos.stage.ci.pipeline.allpackages-pr.package.running","comment_id":null,"namespace":"rpms","nvr":"","original_spec_nvr":"","ref":"x86_64","repo":"standard-test-roles","rev":"PR-7","scratch":true,"status":"SUCCESS","test_guidance":"''","username":null},"msg_id":"2019-b2c3ef1d-175f-4b75-a55b-a2f65c91db97","timestamp":0,"topic":"org.centos.stage.ci.pipeline.allpackages-pr.package.running"}
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // retry
[Pipeline] writeJSON
[Pipeline] archiveArtifacts
[2019-05-13T22:57:55.760Z] Archiving artifacts
[Pipeline] retry
[Pipeline] {
[Pipeline] echo
[2019-05-13T22:57:55.845Z] Checking datagrapper for presence of message...
[Pipeline] sh
[2019-05-13T22:57:56.140Z] + curl --insecure --silent --output /dev/null --write-out '%{http_code}' 'https://apps.stg.fedoraproject.org/datagrepper/id?id=2019-b2c3ef1d-175f-4b75-a55b-a2f65c91db97&chrome=false&is_raw=false'
[Pipeline] echo
[2019-05-13T22:57:56.722Z] 404
[Pipeline] error
[Pipeline] }
[2019-05-13T22:57:56.750Z] ERROR: message not found on datagrepper...
[2019-05-13T22:57:56.751Z] Retrying
[Pipeline] {
[Pipeline] echo
[2019-05-13T22:57:56.799Z] Checking datagrapper for presence of message...
[Pipeline] sh
[2019-05-13T22:57:57.096Z] + curl --insecure --silent --output /dev/null --write-out '%{http_code}' 'https://apps.stg.fedoraproject.org/datagrepper/id?id=2019-b2c3ef1d-175f-4b75-a55b-a2f65c91db97&chrome=false&is_raw=false'
[Pipeline] echo
[2019-05-13T22:57:57.373Z] 404
[Pipeline] error
[Pipeline] }
[2019-05-13T22:57:57.400Z] ERROR: message not found on datagrepper...
[2019-05-13T22:57:57.401Z] Retrying
[Pipeline] {
[Pipeline] echo
[2019-05-13T22:57:57.449Z] Checking datagrapper for presence of message...
[Pipeline] sh
[2019-05-13T22:57:57.745Z] + curl --insecure --silent --output /dev/null --write-out '%{http_code}' 'https://apps.stg.fedoraproject.org/datagrepper/id?id=2019-b2c3ef1d-175f-4b75-a55b-a2f65c91db97&chrome=false&is_raw=false'
[Pipeline] echo
[2019-05-13T22:57:58.024Z] 404
[Pipeline] error
[Pipeline] }
[2019-05-13T22:57:58.086Z] ERROR: message not found on datagrepper...
[2019-05-13T22:57:58.086Z] Retrying
[Pipeline] {
[Pipeline] echo
[2019-05-13T22:57:58.138Z] Checking datagrapper for presence of message...
[Pipeline] sh
[2019-05-13T22:57:58.436Z] + curl --insecure --silent --output /dev/null --write-out '%{http_code}' 'https://apps.stg.fedoraproject.org/datagrepper/id?id=2019-b2c3ef1d-175f-4b75-a55b-a2f65c91db97&chrome=false&is_raw=false'
[Pipeline] echo
[2019-05-13T22:57:58.712Z] 404

@pingou does ci in staging go to the staging bus? Or is this something where we cross busses? Or any ideas who could look into this best?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

4 months ago

The fedmsg relay for stage was running, but stuck.

I restarted the service, let's see if that fixes things.

Metadata Update from @bstinson:
- Issue assigned to bstinson
- Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)

4 months ago

thanks, it is working well now.

Metadata Update from @bgoncalv:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 months ago

Login to comment on this ticket.

Metadata