On Tue, Jul 4, 2017 at 11:41 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > On 07/04/2017 03:46 PM, Adam Williamson wrote: >> On Tue, 2017-07-04 at 09:32 +0200, Christian Dersch wrote: >>> Looks like one compose failed *again* for some mirror issue… This time >>> it is Robotic [1] , but i've seen these random failures several times, >>> also for Astronomy for example. So a new compose should be done here to >>> ensure the Spin gets in properly, >> >> We don't re-spin for non-blocking images as a matter of course. The >> compose process takes far too long for that, unfortunately. >> >> I think nirik said he thought he'd fixed this, but obviously he >> hasn't... > > Yeah, I keep doing things that I think will quash this and then it shows > up again. :( It has been very hard to track down because it's going > through a number of layers... apache to haproxy to varnish to apache. :( Sadly the aarch64 Minimal image also was hit by this :-( _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
