#8962 new robosignatory release/deploy with coreos patches
Closed: Fixed 3 years ago by dustymabe. Opened 3 years ago by dustymabe.

Describe what you would like us to do:


We have a few robosignatory patches that we'd like to get in and deployed:

When do you need this to be done by?


We'd like to sign f32 streams of Fedora CoreOS with the fedora 32 key. Currently our next stream is fedora 32 based, but being signed by the fedora 31 key. We are switching our testing stream over to fedora 32 with the release coming up next week (06/02/2020) and we are switching our stable stream over to fedora 32 in a few weeks time (06/16/2020). It would be nice to have these patches in place for our set of releases next week (so the testing stream is signed with the right key), but not absolutely necessary. However, we'd really really like to have this happen before stable hits fedora 32.


Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, low-trouble, medium-gain

3 years ago

The patches have been merged. Now all we need is a robosignatory release and to deploy it to production. Then we can merge https://pagure.io/fedora-infra/ansible/pull-request/98#

There was a new robosignatory release and it was built in koji python-robosignatory-0.6.7-1.el8.infra (thanks @abompard .

@mohanboddu - can we work on deploying it now?

This work is now complete.

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

3 years ago

Login to comment on this ticket.

Metadata