On Fri, Jun 9, 2017 at 9:37 AM, Jonathan Lebon <jlebon@xxxxxxxxxx> wrote: > Thanks Adam for the quick resolution. Would it be easy to > have an automated workflow to gate these updates on some > quick sanity tests? E.g. push to `:next` first, run some > tests, and then push to `:latest`? +1 That's the plan, we want to wire that up through the new Taskotron container testing stuff but it's just a matter of finding someone with the spare cycles to write the code to do it. > > We're starting to rely more and more on this image in > upstream tests, which means that any image issues can > potentially block up merge queues across multiple projects! > This is both good (horray for adoption) and bad (we have to be more careful not to break things). > I don't want to sound like I'm signing you (nor me) up for > any extra work. Just checking if the infra is already there > for something like this to be implemented straightforwardly. > If yes, then let's log an issue in the > No worries at all, that's certainly something that's desired and something I'd like to see happen. Please file an issue ticket so we can at least get it on the radar more broadly and we can discuss it at a meeting and see if anyone has the cycles to get that going. -AdamM > > ----- Original Message ----- >> On Fri, Jun 9, 2017 at 1:08 AM, Jan Pazdziora <jpazdziora@xxxxxxxxxx> wrote: >> > >> > Hello, >> > >> > it seems registry.fedoraproject.org/fedora:25 was recently updated to >> > some 10 month old version f3535ce68198 where packages cannot be >> > installed due to missing >> > /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-x86_64: >> > >> > https://bugzilla.redhat.com/show_bug.cgi?id=1460094 >> > >> >> Apologies, this was an oversight on my part. I did a sync and >> specified the wrong koji tag to query for the latest base image. This >> should be resolved now, if you have any further issues please let me >> know. >> >> -AdamM >> >> > -- >> > Jan Pazdziora >> > Senior Principal Software Engineer, Identity Management Engineering, Red >> > Hat >> > _______________________________________________ >> > cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx >> > To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx >> _______________________________________________ >> cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx >> > _______________________________________________ > cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
