This was a bad image in nodepool. I've rebuilt the image and killed our pool of workers running the old image and things seem to be ok now. I'm in the process of enqueueing rechecks for every failed turbo-hipster run now, but they'll take some time to all get executed.
Thanks for your patience everyone. Is it possible to add a verification step to nodepool so that it doesn't mark a new image as ready unless it passes some basic sanity checks? Thanks, Michael On Sat, Oct 18, 2014 at 8:44 AM, Michael Still <mi...@stillhq.com> wrote: > Hi, > > I've just noticed that the DB Datasets CI (the artist formerly known > as turbo hipster) is failing for many patches. I'm looking into it > now. > > Michael > > -- > Rackspace Australia -- Rackspace Australia _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev