It look like we hit https://projects.engineering.redhat.com/browse/RHEVINTEG-2523

or at least it looks like it:

<error type="ovirtsdk.infrastructure.errors.RequestError" message="

 status: 409

 reason: Conflict

 detail: Cannot add VM. The VM name is already in use, please choose a unique name and try again.">

re-trigger?

On Tue, Jul 17, 2018 at 5:04 PM RHV-CI Jenkins <jenkins@ovirt.org> wrote:

A system test invoked by the "rhv-master" change queue including change
144186,1 (ds-vdsm) failed. However, this change seems not to be the root cause
for this failure. Change 128563,2 (ds-vdsm) that this change depends on or is
based on, was detected as the cause of the testing failures.

This change had been removed from the testing queue. Artifacts built from this
change will not be released until either change 128563,2 (ds-vdsm) is fixed and
this change is updated to refer to or rebased on the fixed version, or this
change is modified to no longer depend on it.

For further details about the change see:
https://code.engineering.redhat.com/gerrit/#/c/144186/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://code.engineering.redhat.com/gerrit/#/c/128563/2

For failed test results see:
https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv-master_change-queue-tester/92/

--

Emil Natan

RHV DevOps