On Sat, Oct 18, 2014 at 11:02 AM, Jeremy Stanley wrote:
> On 2014-10-18 10:45:23 +1100 (+1100), Michael Still wrote:
> [...]
>> 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?
>
> Back in the before
On 2014-10-18 10:45:23 +1100 (+1100), Michael Still wrote:
[...]
> 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?
Back in the beforetime, when devstack-gate had scripts which managed
the worker pool
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 eve
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
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://li
