#8002 Help to figure out what is going on with robosignatory in staging
Closed: Fixed 4 months ago by kevin. Opened 4 months ago by pingou.

I have just built python-arrow-0.12.1-16.fc31 in staging koji, looking at koji -s https://koji.stg.fedoraproject.org/kojihub buildinfo python-arrow-0.12.1-16.fc31 it is still in Tags: f31-updates-candidate while I was expecting that robosignatory would have picked it up from this tag and moved to f31-updates-testing-pending.

Could someone help me debug this?


Looks like a signing problem:

● fedmsg-hub.service - Generic fedmsg processing hub
Loaded: loaded (/usr/lib/systemd/system/fedmsg-hub.service; enabled; vendor preset: disabled
)
Drop-In: /etc/systemd/system/fedmsg-hub.service.d
└─systemd.conf
Active: active (running) since Tue 2019-07-16 14:43:12 UTC; 53min ago
Docs: https://fedmsg.readthedocs.org/
Main PID: 27802 (fedmsg-hub)
CGroup: /system.slice/fedmsg-hub.service
├─27802 /usr/bin/python2 /usr/bin/fedmsg-hub
├─28888 /usr/bin/python /usr/share/sigul/client.py --batch --user-name autopen --pas
sphrase-file /etc/sigul/autosign.pass --config-file /etc/sigul/client.conf sign-rpms --store-in
-koji --koji-only -k primary --v3-signature testkey python3-arrow-0.12.1-16.fc31.noarch python2
-arrow-0.12.1-16.fc31.noarch python-arrow-0.12.1-16.fc31.src
└─28889 /usr/bin/python /usr/share/sigul/client.py --batch --user-name autopen --pas
sphrase-file /etc/sigul/autosign.pass --config-file /etc/sigul/client.conf sign-rpms --store-in
-koji --koji-only -k primary --v3-signature testkey python3-arrow-0.12.1-16.fc31.noarch python2
-arrow-0.12.1-16.fc31.noarch python-arrow-0.12.1-16.fc31.src

ie, it's stuck calling sigul client.

Fixed.

This was a combo of the sign-vault having died and the dest tag having the wrong perms. It's working now.

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

4 months ago

Login to comment on this ticket.

Metadata