On Fri, Oct 11, 2019 at 3:52 PM Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > > On Fri, Oct 11, 2019 at 03:47:00PM +0100, Peter Robinson wrote: > > On Fri, Oct 11, 2019 at 2:41 PM Aurelien Bompard > > <abompard@xxxxxxxxxxxxxxxxx> wrote: > > > > > > Hey folks, > > > > > > Last Monday, before the freeze, we updated Robosignatory in prod with a few new features, some of which could not be tested in staging as thoroughly as we wanted to. As a result, the version currently in prod has issues with the CoreOS artifacts. We've worked on that and our tests in staging are now entirely successful, that why I'm asking for a freeze break to update robosignatory to the latest code (0.6.5) and make some adjustments to the configuration file in ansible (patch attached). > > > > It also had issues with signing IoT composes so could we make sure > > that works at the end of this please. > > Is that something that could be tested in staging? > Happy to assist there if I can. TBH I have no idea. Does that require a completely different compose to be run on the staging infra with testing keys etc? _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
