fedora-infrastructure

#8619 robotsignatory tracebacking in staging for FCoreOS
Closed: Invalid by dustymabe. Opened by pingou.

Closed: Invalid
Reopen Issue

On autosign01.stg.phx2.fedoraproject.org I'm seeing the following traceback in the logs:

[fedora_messaging.twisted.protocol INFO] Consuming message from topic org.fedoraproject.stg.coreos.build.request.ostree-sign (message id f775f5de-4fc9-4ee0-8e7b-ac1c2b8ea422)
[robosignatory INFO] Received message from fedora-messaging with topic: org.fedoraproject.stg.coreos.build.request.ostree-sign
[robosignatory ERROR] u'stream': Unable to handle message: Id: f775f5de-4fc9-4ee0-8e7b-ac1c2b8ea422
Topic: org.fedoraproject.stg.coreos.build.request.ostree-sign
Headers: {
"fedora_messaging_schema": "base.message",
"fedora_messaging_severity": 20,
"sent-at": "2020-02-04T22:05:35+00:00"
}
Body: {
"basearch": "x86_64",
"build_id": "31.20200204.dev.1",
"checksum": "sha256:81143f88f2859487f58d69381c9e74a2528fd46c7a0e1b1fd312c6e47338a32e",
"commit_object": "s3://fcos-builds/devel/dustymabe/tmp/builds/tmp/ostree-commit-object",
"request_id": "b9af9315-24d4-4ea3-8008-2f23e295f937"
}
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/robosignatory/consumer.py", line 51, in __call__
self.coreos_handler.consume(msg)
File "/usr/lib/python2.7/site-packages/robosignatory/coreos.py", line 49, in consume
'%(build_id)s on %(stream)s for %(basearch)s' % msg.body
KeyError: u'stream'
[fedora_messaging.twisted.protocol WARNING] Returning message id f775f5de-4fc9-4ee0-8e7b-ac1c2b8ea422 to the queue

@abompard any thought on this?

@dustymabe do you know if something changed in the messages sent? From a closer look at this, it seems there is a field stream missing.

I'll look into this. I am trying to test some changes to our code that sends the request to robosignatory and I indeed and failing to send the stream information. Although I wonder if it's really required. Will look into it.

Just going to copy from the IRC log:

10:56:26 < jlebon> that's a failure on my part, i should've told you you need to add e.g. `--extra-fedmsg-keys stream=testing-devel`, though clearly robosignatory should handle it more gracefully

So I think the bug here is essentially that last bit.

Actually, let's do https://pagure.io/robosignatory/pull-request/43 instead!

we can close this because it was a misconfiguration on my end and robosignatory in stage is not misbehaving.

Metadata Update from @dustymabe:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.