Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

There were 2 different issues, which seem to be resolved now in [1], OST on 'master' branch are running successfully in the past 4 builds. If you still have the issue check that you are using the latest commit. Thanks everyone for the effort. [1] https://gerrit.ovirt.org/#/c/65849 [2]

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

Michal, Is it known issue? Thanks, Piotr 29 paź 2016 18:24 "Yaniv Kaul" napisał(a): > IDK - still fails for me, though on potentiall different issue: > Cluster creation fails with: > RequestError: > status: 400 > reason: Bad Request > detail: Cannot create Cluster. The

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

IDK - still fails for me, though on potentiall different issue: Cluster creation fails with: RequestError: status: 400 reason: Bad Request detail: Cannot create Cluster. The chosen CPU is not supported. The chosen CPU is the same CPU I've used for several weeks now... Engine.log shows:

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

And now the CI job is [finally] passing. Piotr/Eli - the stomp timeout may be worth investigating, but it's definitely NOT the root cause of the previous failures, so feel free to deprioritize it as you see fit. Thanks to everyone who helped debug/investigate/review these issues, and sorry for

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

Thanks, not what I would expect from a pure and simple @NotNull meant as a hint for FindBugs... Can somebody from infra help me to understand what actually happened there? Because it choked on a direct call to a method (well, there is probably CDI proxy in there somewhere). Something had to

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

The 004 CI is now passing, and it fails on 006. I merged a patch for the failure, let's see where we get next. On Thu, Oct 27, 2016 at 3:13 PM, Allon Mureinik wrote: > Now I also see it in the CI. > > I merged the patch so we can squeeze in as many CI runs as possible

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

Now I also see it in the CI. I merged the patch so we can squeeze in as many CI runs as possible before the weekend. On Thu, Oct 27, 2016 at 11:38 AM, Allon Mureinik wrote: > [Adding Martin Sivak.] > > That reproduces on my setup too, but didn't see it in CI, and is not >

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

[Adding Martin Sivak.] That reproduces on my setup too, but didn't see it in CI, and is not related to the recent injection issues. Martin - This issue seems to have been introduced in your patch 0e4ae6b. I'm not sure eaxctly why java doesn't like the @NotNull annotation on schedule, but

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

Eli, Please take a look. Thanks, Piotr On Thu, Oct 27, 2016 at 8:12 AM, Yaniv Kaul wrote: > I still fail to run a VM: > 2016-10-27 02:01:02,849 ERROR [org.ovirt.engine.core.bll.RunVmOnceCommand] > (default task-17) [78897d21] Command >

Re: [ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

@Infra - the last experimental job I saw was from ~17:30 local Israel time. Any idea why another one isn't being triggered (or am I just being daft)? On Wed, Oct 26, 2016 at 6:27 PM, Allon Mureinik wrote: > Yipes. > [1] should fix that, waiting for the CI to run to merge. >

[ovirt-devel] Failure on start VM in ovirt-system-tests from patches merged to master on the 25/10/2016

Hi, We have new failure on OST from patches merged to master yesterday, the failure started after the merge of [1], but as there were quite a few patches merged quickly I can't make sure it is the one causing it(OST aren't ran per-patch). The test that fails is [2] when attempting to start the VM.