@kevin noted that bodhi-push seems to be refreshing the signed status of every build on each run. I looked at the logs for the bodhi messages consumers running on OpenShift, and they do not seem to be logging buildsys.tag message topics being received.
buildsys.tag
I think I configured that correctly here:
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/openshift-apps/bodhi.yml#n16
and here:
https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/bodhi2/base/templates/fedora-messaging.toml.j2#n45
And I do see koji tag messages ending up here:
https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.buildsys.tag&delta=3600
Since I don't have admin access to much, it is difficult for me to debug this much further on my own.
Can someone take at look at the RabbitMQ server and see if my bodhi queue is correctly bound to the org.fedoraproject.*.buildsys.tag topic?
org.fedoraproject.*.buildsys.tag
Here's the bindings I see:
amq.topic exchange bodhi_composer queue org.fedoraproject..bodhi.composer.start [] amq.topic exchange bodhi queue org.fedoraproject..bodhi.update.edit [] amq.topic exchange bodhi queue org.fedoraproject..bodhi.update.request.testing [] amq.topic exchange bodhi queue org.fedoraproject..buildsys.tag []
Perhaps this is related to the koji.stg using fedora-messaging and prod koji using fedmsg?
It sounds like this is due to https://github.com/fedora-infra/bodhi/issues/3304 - I think we can close this issue. It sounds like things will start working as expected once Koji in production sends the new message formats, and bodhi-push knows how to find out if builds are signed in the meantime. The only real downside is that it makes bodhi-push slower, and that it prints warning messages.
Metadata Update from @bowlofeggs: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.