Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288

On Mon, Sep 19, 2016 at 8:49 PM, Eyal Edri wrote: > Is this the usual Sanlock issue? "Usual" sanlock issue is alarming. I don't know about any issues with Sanlock. Do we have a bug about this? > > Error Message > > status: 400 > reason: Bad Request > detail: Cannot add VM:

Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288

t;infra" <infra@ovirt.org>, > "Simone Tiraboschi" <stira...@redhat.com> > Sent: Monday, September 19, 2016 8:49:59 PM > Subject: Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288 > > Is this the usual Sanlock issue? > > Error Message >

Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288

Message - From: "Eyal Edri" <ee...@redhat.com> To: "Lev Veyde" <lve...@redhat.com> Cc: "Sandro Bonazzola" <sbona...@redhat.com>, "infra" <infra@ovirt.org>, "Simone Tiraboschi" <stira...@redhat.com> Sent: Monday, Septem

Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288

I really want to add this job to the experimental flow to catch regressions early, but we have to iron out any false positives or errors we're seeing before that. Until now I was only aware of the Sanlock issue, which should be resolved soon once its available in centos. Are we aware of other

Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288

On Mon, Sep 19, 2016 at 7:49 PM, Eyal Edri wrote: > Is this the usual Sanlock issue? > Not that sure, however build 289 come back to stable by itself. > > Error Message > > status: 400 > reason: Bad Request > detail: Cannot add VM: Storage Domain cannot be accessed. >

Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288

Is this the usual Sanlock issue? Error Message status: 400 reason: Bad Request detail: Cannot add VM: Storage Domain cannot be accessed. -Please check that at least one Host is operational and Data Center state is up. Stacktrace Traceback (most recent call last): File