On 2017-01-11 20:40:26 -0600 (-0600), Matt Riedemann wrote:
[...]
> Well I guess it's less sinister than all that, it was just a matter of when
> the nova change landed, which was meant for newton but happened in Ocata:
[...]
Oh, good catch! I didn't even think to check whether that hook
existed
On 1/11/2017 8:18 PM, Matt Riedemann wrote:
On 1/11/2017 9:19 AM, Jeremy Stanley wrote:
If you look in the _zuul_ansible/scripts directory you'll see that
shell script which exited nonzero is the one calling devstack-gate,
so we've got something broken near the end of the job as you
surmise. I
On 1/11/2017 9:19 AM, Jeremy Stanley wrote:
If you look in the _zuul_ansible/scripts directory you'll see that
shell script which exited nonzero is the one calling devstack-gate,
so we've got something broken near the end of the job as you
surmise. I think it might be the post_test_hook:
On 1/11/2017 7:17 AM, Sylvain Bauza wrote:
On a separate change, I also have the placement job being -1 because of
the ComputeFilter saying that the service is disabled because of
'connection of libvirt lost' :
On 2017-01-10 20:03:28 -0500 (-0500), Matt Riedemann wrote:
> I'm trying to sort out failures in the placement job in stable/newton job
> where the tests aren't failing but it's something in the host cleanup step
> that blows up.
>
> Looking here I see this:
>
>
Le 11/01/2017 02:03, Matt Riedemann a écrit :
> I'm trying to sort out failures in the placement job in stable/newton
> job where the tests aren't failing but it's something in the host
> cleanup step that blows up.
>
> Looking here I see this:
>
>
I'm trying to sort out failures in the placement job in stable/newton
job where the tests aren't failing but it's something in the host
cleanup step that blows up.
Looking here I see this: