fedora-infrastructure

#8118 robosignatory broken in staging?
Closed: Fixed by kevin. Opened by pingou.

Closed: Fixed
Reopen Issue

I've made two builds this morning: fedora-gather-easyfix-0.1.1-38.fc31 and fedora-gather-easyfix-0.1.1-39.fc31 and looking at : koji -s https://koji.stg.fedoraproject.org/kojihub buildinfo fedora-gather-easyfix-0.1.1-39.fc31 fedora-gather-easyfix-0.1.1-38.fc31 they seem to be both stuck in f31-updates-candidate.

Is robosignatory stuck in staging?

Just my 2 cents but I think we should not close this ticket until we have a nagios alert for robosignatory.

Is robosignatory deployed using fedora-messaging ? If so we could monitor the size of the queue.

Is robosignatory deployed using fedora-messaging ?

Not yet

Fixed.

This was due to our update/reboots yesterday... needed to restart the vault, the bridge and retag the builds.

:art:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- 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.