February 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit
by Eyal Edri (oVirt JIRA) 20 Feb '19

20 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1767: ---------------------------------- I agree we don't have capacity or resources that justify going into such project now, just because gitweb isn't amazing and OK with closing it. but it has nothing to do with the GitHub mirroring. > Look into replacing gitweb for oVirt Gerrit > ------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: Icebox, gerrit > > One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ > Another plugin to consider is the one for using GitBlit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitblit is another Java based Gir bowser: > http://gitblit.com/features.html -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

2 1

[CQ]: 97861, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Feb '19

20 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97861,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97886,2 (ovirt-engine) 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 97886,2 (ovirt-engine) 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://gerrit.ovirt.org/#/c/97861/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97886/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13053/

1 0

[CQ]: 97862, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Feb '19

20 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97862,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97886,2 (ovirt-engine) 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 97886,2 (ovirt-engine) 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://gerrit.ovirt.org/#/c/97862/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97886/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13050/

1 0

[CQ]: 97845,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 20 Feb '19

20 Feb '19

Change 97845,4 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97845/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13045/

1 0

[CQ]: 97906, 1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Feb '19

20 Feb '19

A system test invoked by the "ovirt-4.3" change queue including change 97906,1 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 97519,2 (ovirt-node-ng-image) 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 97519,2 (ovirt-node-ng-image) 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://gerrit.ovirt.org/#/c/97906/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97519/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/58/

1 0

[CQ]: 97826, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Feb '19

20 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97826,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97886,2 (ovirt-engine) 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 97886,2 (ovirt-engine) 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://gerrit.ovirt.org/#/c/97826/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97886/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13042/

1 0

[CQ]: 97888, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Feb '19

20 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97888,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97886,2 (ovirt-engine) 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 97886,2 (ovirt-engine) 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://gerrit.ovirt.org/#/c/97888/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97886/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13038/

1 0

oVirt infra daily report - unstable production jobs - 741
by jenkins＠jenkins.phx.ovirt.org 20 Feb '19

20 Feb '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/741//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97886,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 19 Feb '19

19 Feb '19

Change 97886,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97886/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13034/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Failed to run project_setup.sh for: #3668 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-46q2c.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Failed to run project_setup.sh for: #3666 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-t62ck.

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc28-x86_64 #883
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

1 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Failed to run project_setup.sh for: #3664 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-c73h3.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Failed to run project_setup.sh for: #3663 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-1s9z1.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Failed to run project_setup.sh for: #3659 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-vvnnr.

1 0

Re: [ovirt-devel] Re: ovirt-engine has been tagged (ovirt-engine-4.3.1)
by Sandro Bonazzola 19 Feb '19

19 Feb '19

Il giorno mar 19 feb 2019 alle ore 15:59 Tal Nisan <tnisan(a)redhat.com> ha scritto: > > > On Tue, Feb 19, 2019 at 1:22 PM Greg Sheremeta <gshereme(a)redhat.com> > wrote: > >> >> >> On Tue, Feb 19, 2019 at 4:41 AM Tal Nisan <tnisan(a)redhat.com> wrote: >> >>> >>> >>> On Tue, Feb 19, 2019 at 11:30 AM Doron Fediuck <dfediuck(a)redhat.com> >>> wrote: >>> >>>> >>>> >>>> On Tue, 19 Feb 2019 at 11:14, Tal Nisan <tnisan(a)redhat.com> wrote: >>>> >>>>> >>>>> >>>>> On Tue, Feb 19, 2019 at 11:03 AM Doron Fediuck <dfediuck(a)redhat.com> >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Tue, 19 Feb 2019 at 10:56, Tal Nisan <tnisan(a)redhat.com> wrote: >>>>>> >>>>>>> OK seems like I've found the reason, Ori you merged this patch >>>>>>> between the time when the version bumps were pushed and their actual merge >>>>>>> which cause them to rebase on the broken patch - >>>>>>> https://gerrit.ovirt.org/#/c/96610/ >>>>>>> Note that Jenkins failed on patchset 12 while CI was marked as +1 >>>>>>> manually (I guess wrongly based on the fact the artifacts were successfully >>>>>>> build but that does not mean tests passed) >>>>>>> >>>>>>> >>>>>> As a next step I'd like to know how do we avoid it next time? >>>>>> >>>>> Really hard to avoid, there's not many chance for that to happen since >>>>> the time window is quite short, if we decide to keep on rebasing the >>>>> version bumps it will not help much because Jenkins is still taking quite a >>>>> lot of time and potentially broken patches can be merged at this point. >>>>> What we can do is set a no-merge time in this specific time frame >>>>> (only if building from master, on the stable branches the maintainers take >>>>> care of all merges so no problem there) in which no one will merge patches >>>>> to keep stability >>>>> >>>> >>>> Will a maintainers' mailing list (single for all ovirt projects) help >>>> here or would we prefer a mutex somewhere? >>>> >>> Given the short time window in which this can happen I think the devel >>> list should do, a short email of "build is about to go soon, please hold >>> your merges until engine has been tagged" will probably be enough >>> >> >> I've found that many developers filter devel and other mailing lists into >> labels and infrequently check them. Not sure this will work. >> > That's a pity, it means no list will actually work cause the same people > who filter devel will filter the others. > Sando, any easy way in Gerrit to disable merges to a certain project and > then bring it back? > > No idea, adding infra > >> >>> >>>>>> >>>>>>> >>>>>>> On Tue, Feb 19, 2019 at 10:50 AM Tal Nisan <tnisan(a)redhat.com> >>>>>>> wrote: >>>>>>> >>>>>>>> I don't get it, both version bump patches passed Jenkins with all >>>>>>>> unit tests: >>>>>>>> https://gerrit.ovirt.org/#/c/97835 >>>>>>>> And the Jenkins job: >>>>>>>> >>>>>>>> https://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/48… >>>>>>>> >>>>>>>> Fred, what is the suspected patch that broke the tests? I suspect >>>>>>>> Gerrit auto rebase might broke something in case the version bump patches >>>>>>>> were not fully rebased on master when they were pushed >>>>>>>> >>>>>>>> On Tue, Feb 19, 2019 at 9:51 AM Fred Rolland <frolland(a)redhat.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> This fixes the failing test: >>>>>>>>> https://gerrit.ovirt.org/#/c/97865/ >>>>>>>>> >>>>>>>>> On Tue, Feb 19, 2019 at 9:28 AM Benny Zlotnik <bzlotnik(a)redhat.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I created a revert patch last night: >>>>>>>>>> https://gerrit.ovirt.org/#/c/97854/ >>>>>>>>>> >>>>>>>>>> frolland is currently checking if it's easy to fix without >>>>>>>>>> reverting >>>>>>>>>> >>>>>>>>>> On Tue, Feb 19, 2019, 09:18 Sandro Bonazzola <sbonazzo(a)redhat.com >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> please note engine build failed with: >>>>>>>>>>> >>>>>>>>>>> *17:45:54* [ERROR] Tests run: 11, Failures: 0, Errors: 3, Skipped: 1, Time elapsed: 0.258 s <<< FAILURE! - in org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest*17:45:54* [ERROR] testAdd Time elapsed: 0.027 s <<< ERROR!*17:45:54* org.ovirt.engine.api.restapi.utils.MappingException: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAdd(BackendAttachedStorageDomainsResourceTest.java:75)*17:45:54* Caused by: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAdd(BackendAttachedStorageDomainsResourceTest.java:75)*17:45:54* Caused by: java.lang.NullPointerException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAdd(BackendAttachedStorageDomainsResourceTest.java:75)*17:45:54* *17:45:54* [ERROR] testList Time elapsed: 0.018 s <<< ERROR!*17:45:54* org.ovirt.engine.api.restapi.utils.MappingException: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.getCollection(BackendAttachedStorageDomainsResourceTest.java:251)*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testList(BackendAttachedStorageDomainsResourceTest.java:179)*17:45:54* Caused by: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.getCollection(BackendAttachedStorageDomainsResourceTest.java:251)*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testList(BackendAttachedStorageDomainsResourceTest.java:179)*17:45:54* Caused by: java.lang.NullPointerException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.getCollection(BackendAttachedStorageDomainsResourceTest.java:251)*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testList(BackendAttachedStorageDomainsResourceTest.java:179)*17:45:54* *17:45:54* [ERROR] testAddByName Time elapsed: 0.022 s <<< ERROR!*17:45:54* org.ovirt.engine.api.restapi.utils.MappingException: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAddByName(BackendAttachedStorageDomainsResourceTest.java:116)*17:45:54* Caused by: java.lang.reflect.InvocationTargetException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAddByName(BackendAttachedStorageDomainsResourceTest.java:116)*17:45:54* Caused by: java.lang.NullPointerException*17:45:54* at org.ovirt.engine.api.restapi.resource.BackendAttachedStorageDomainsResourceTest.testAddByName(BackendAttachedStorageDomainsResourceTest.java:116)*17:45:54* *17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.LinkFollowerTest*17:45:54* [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 s - in org.ovirt.engine.api.restapi.util.LinkFollowerTest*17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.FenceOptionsParserTest*17:45:54* ERROR org.ovirt.engine.api.restapi.util.FenceOptionsParser - No type specified for fencing option "one".*17:45:54* ERROR org.ovirt.engine.api.restapi.util.FenceOptionsParser - Invalid fencing option description "three".*17:45:54* ERROR org.ovirt.engine.api.restapi.util.FenceOptionsParser - Invalid fencing agent description "foo:::one=1,two=2,three=3".*17:45:54* [INFO] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 s - in org.ovirt.engine.api.restapi.util.FenceOptionsParserTest*17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.LinkHelperTest*17:45:54* [INFO] Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 s - in org.ovirt.engine.api.restapi.util.LinkHelperTest*17:45:54* [INFO] Running org.ovirt.engine.api.restapi.util.QueryHelperTest*17:45:54* [INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in org.ovirt.engine.api.restapi.util.QueryHelperTest*17:45:55* [INFO] *17:45:55* [INFO] Results:*17:45:55* [INFO] *17:45:55* [ERROR] Failures: *17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemoveCantDo:181->doTestBadRemove:203 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemoveFailed:186->doTestBadRemove:203 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendStorageDomainResourceTest.testConflictedUpdate:175 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendStorageDomainResourceTest.testUpdateCantDo:145->doTestBadUpdate:164 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] BackendStorageDomainResourceTest.testUpdateFailed:150->doTestBadUpdate:164 Unexpected exception type thrown ==> expected: <javax.ws.rs.WebApplicationException> but was: <org.ovirt.engine.api.restapi.utils.MappingException>*17:45:55* [ERROR] Errors: *17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testGet:69 ? Mapping java.lang.reflec...*17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemove:152 ? Mapping java.lang.re...*17:45:55* [ERROR] BackendAttachedStorageDomainResourceTest.testRemoveLocalStorage:176 ? Mapping ...*17:45:55* [ERROR] BackendAttachedStorageDomainsResourceTest.testAdd:75 ? Mapping java.lang.refle...*17:45:55* [ERROR] BackendAttachedStorageDomainsResourceTest.testAddByName:116 ? Mapping java.lan...*17:45:55* [ERROR] BackendAttachedStorageDomainsResourceTest.testList:179->getCollection:251 ? Mapping*17:45:55* [ERROR] BackendStorageDomainResourceTest.testGet:79 ? Mapping java.lang.reflect.Invoca...*17:45:55* [ERROR] BackendStorageDomainResourceTest.testGetFcp:91 ? Mapping java.lang.reflect.Inv...*17:45:55* [ERROR] BackendStorageDomainResourceTest.testUpdate:140 ? Mapping java.lang.reflect.In...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddExistingStorageDomain:169->doTestAddStorageDomain:211 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddIscsiStorageDomain:348 ? Mapping java...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddIscsiStorageDomainAssumingConnection:392 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddLocalStorageDomain:251 ? Mapping java...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddPosixStorageDomain:301 ? Mapping java...*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddStorageDomain:82->doTestAddStorageDomain:211 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddStorageDomainWithExistingConnectionId:128 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest.testAddStorageDomainWithHostName:162->doTestAddStorageDomain:211 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest>AbstractBackendCollectionResourceTest.testList:72->getCollection:634 ? Mapping*17:45:55* [ERROR] BackendStorageDomainsResourceTest>AbstractBackendCollectionResourceTest.testQuery:81->getCollection:634 ? Mapping*17:45:55* [INFO] *17:45:55* [ERROR] Tests run: 1849, Failures: 5, Errors: 19, Skipped: 65*17:45:55* [INFO] *17:45:55* [INFO] ------------------------------------------------------------------------*17:45:55* [INFO] Reactor Summary:*17:45:55* [INFO] *17:45:55* [INFO] oVirt Findbugs Filters ............................ SUCCESS [1.970s]*17:45:55* [INFO] ovirt-root ........................................ SUCCESS [3.307s]*17:45:55* [INFO] oVirt Build Tools root ............................ SUCCESS [1.213s]*17:45:55* [INFO] oVirt checkstyle .................................. SUCCESS [2.121s]*17:45:55* [INFO] oVirt Checkstyle Checks ........................... SUCCESS [3.430s]*17:45:55* [INFO] oVirt Modules - backend ........................... SUCCESS [0.734s]*17:45:55* [INFO] oVirt Manager ..................................... SUCCESS [0.738s]*17:45:55* [INFO] oVirt Engine dependencies ......................... SUCCESS [0.891s]*17:45:55* [INFO] oVirt Engine common dependencies .................. SUCCESS [3.350s]*17:45:55* [INFO] oVirt Engine tools dependencies ................... SUCCESS [0.813s]*17:45:55* [INFO] Utilities to extend java.logging framework ........ SUCCESS [1.682s]*17:45:55* [INFO] Extensions API root ............................... SUCCESS [0.005s]*17:45:55* [INFO] ovirt-engine-extensions-api ....................... SUCCESS [9.274s]*17:45:55* [INFO] oVirt Modules - manager ........................... SUCCESS [2.056s]*17:45:55* [INFO] Universal utilities ............................... SUCCESS [20.282s]*17:45:55* [INFO] Extensions manager ................................ SUCCESS [5.412s]*17:45:55* [INFO] GWT UI Compatibility .............................. SUCCESS [6.178s]*17:45:55* [INFO] Common Code ....................................... SUCCESS [36.381s]*17:45:55* [INFO] Common utilities .................................. SUCCESS [35.291s]*17:45:55* [INFO] Branding package .................................. SUCCESS [9.146s]*17:45:55* [INFO] ovirt-engine sso .................................. SUCCESS [5.829s]*17:45:55* [INFO] Data Access Layer ................................. SUCCESS [30.876s]*17:45:55* [INFO] engine scheduler bean ............................. SUCCESS [6.888s]*17:45:55* [INFO] Vds broker ........................................ SUCCESS [32.916s]*17:45:55* [INFO] builtin-extensions ................................ SUCCESS [2.320s]*17:45:55* [INFO] Search Backend .................................... SUCCESS [10.064s]*17:45:55* [INFO] Backend Authentication, Authorization and Accounting SUCCESS [7.355s]*17:45:55* [INFO] Custom Application Server Authentication Plugin ... SUCCESS [3.320s]*17:45:55* [INFO] Backend Logic @Service bean ....................... SUCCESS [2:51.560s]*17:45:55* [INFO] oVirt RESTful API Backend Integration ............. SUCCESS [1.084s]*17:45:55* [INFO] oVirt RESTful API interface ....................... SUCCESS [1.005s]*17:45:55* [INFO] oVirt Engine API Definition ....................... SUCCESS [50.498s]*17:45:55* [INFO] oVirt Engine API Commom Parent POM ................ SUCCESS [1.037s]*17:45:55* [INFO] oVirt Engine API Common JAX-RS .................... SUCCESS [8.077s]*17:45:55* [INFO] oVirt RESTful API Backend Integration Type Mappers SUCCESS [22.779s]*17:45:55* [INFO] oVirt RESTful API Backend Integration JAX-RS Resources FAILURE [1:52.179s] >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Job is here: >>>>>>>>>>> https://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_6… >>>>>>>>>>> >>>>>>>>>>> So we need a respin once fixed. >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> SANDRO BONAZZOLA >>>>>>>>>>> >>>>>>>>>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>>>>>>>>>> >>>>>>>>>>> Red Hat EMEA <https://www.redhat.com/> >>>>>>>>>>> >>>>>>>>>>> sbonazzo(a)redhat.com >>>>>>>>>>> <https://red.ht/sig> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Devel mailing list -- devel(a)ovirt.org >>>>>>>>>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>>>>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>>>>>> oVirt Code of Conduct: >>>>>>>>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>>>>>>>> List Archives: >>>>>>>>>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/2GJAJHWAD5X43… >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Devel mailing list -- devel(a)ovirt.org >>>>>>>>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>>>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>>>>> oVirt Code of Conduct: >>>>>>>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>>>>>>> List Archives: >>>>>>>>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/32XDCPM6IPOD7… >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Devel mailing list -- devel(a)ovirt.org >>>>>>>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>>>> oVirt Code of Conduct: >>>>>>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>>>>>> List Archives: >>>>>>>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/LV6XFFQPI4ZFZ… >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>> Devel mailing list -- devel(a)ovirt.org >>>>>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>>>> oVirt Code of Conduct: >>>>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>>>> List Archives: >>>>>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/THBBN6G2ETAEE… >>>>>>> >>>>>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZG57PMU7GKJ57… >>> >> >> >> -- >> >> GREG SHEREMETA >> >> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX >> >> Red Hat NA >> >> <https://www.redhat.com/> >> >> gshereme(a)redhat.com IRC: gshereme >> <https://red.ht/sig> >> > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

3 2

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Failed to run project_setup.sh for: #3659 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-w4zcq.

1 0

[CQ]: 96986, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96986,17 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (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 97775,2 (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://gerrit.ovirt.org/#/c/96986/17 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13028/

1 0

[CQ]: 96743, 5 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96743,5 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 97817,1 (ovirt-provider-ovn) 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 97817,1 (ovirt-provider-ovn) 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://gerrit.ovirt.org/#/c/96743/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97817/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13023/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Failed to run project_setup.sh for: #3650 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-2flgx.

1 0

[CQ]: 07c7fd2 (ovirt-web-ui) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

A system test invoked by the "ovirt-master" change queue including change 07c7fd2 (ovirt-web-ui) failed. However, this change seems not to be the root cause for this failure. Change 7d67266 (ovirt-web-ui) 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 7d67266 (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/07c7fd24e2ae3d824a60a6951ceb97… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-web-ui/commit/7d6726676871274417e78139507a96… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13018/

1 0

[CQ]: 96610, 13 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96610,13 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97719,3 (ovirt-engine) 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 97719,3 (ovirt-engine) 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://gerrit.ovirt.org/#/c/96610/13 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97719/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13013/

1 0

[CQ]: 97677,7 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 19 Feb '19

19 Feb '19

Change 97677,7 (ovirt-engine-sdk) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97677/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13009/

1 0

[CQ]: 97818, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 19 Feb '19

19 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97818,1 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 97817,1 (ovirt-provider-ovn) 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 97817,1 (ovirt-provider-ovn) 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://gerrit.ovirt.org/#/c/97818/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97817/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13004/

1 0

oVirt infra daily report - unstable production jobs - 740
by jenkins＠jenkins.phx.ovirt.org 19 Feb '19

19 Feb '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/740//artifact/exported-a… Cheers, Jenkins

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3643 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-052rf.

1 0

[CQ]: 97818, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97818,1 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 97817,1 (ovirt-provider-ovn) 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 97817,1 (ovirt-provider-ovn) 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://gerrit.ovirt.org/#/c/97818/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97817/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13000/

1 0

[CQ]: 97821, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97821,1 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 97819,1 (ovirt-host) 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 97819,1 (ovirt-host) 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://gerrit.ovirt.org/#/c/97821/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97819/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12996/

1 0

[CQ]: 97817, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 97817,1 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97817/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12992/

1 0

[CQ]: 97817, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 97817,1 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97817/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12988/

1 0

[vdsm]jenkins build on demand doesn't seem to work on stable branch
by Francesco Romani 18 Feb '19

18 Feb '19

Hi Infra, I'd like to build RPMs using "ci please build" for my https://gerrit.ovirt.org/#/c/97737/ - the ultimate goal is to have OST validate my patch. It seems to me that the "ci please build" command isn't working, or at least I can't see any feedback about it. Is this automation still enabeld for the stable branch? Any idea what's going on? Thanks, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

2 2

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3635 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-h0snq.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3635 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-h540s.

1 0

[CQ]: 97820, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97820,1 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 97819,1 (ovirt-host) 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 97819,1 (ovirt-host) 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://gerrit.ovirt.org/#/c/97820/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97819/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12984/

1 0

After import storage many of my vm's disks not appear
by Kalil de A. Carvalho 18 Feb '19

18 Feb '19

Hello all. It is been a while that I used the oVirt and on the same time, the company where I started to work, has a big problem with the engine, we lose it. We did not have any backup. To try recovery the enverioment I installed a knew oVirt, this time Hosted Engine, and import the Storage. I could import and start some vm's but the most part not appear for me, dosen't show on "Disk Import", "VM Import" and any place. I know that is there, because show me that size. May I see, like list, this disks? I can't do this throught oVirt web. Is there any way to bring dist disks back? I already search this tasks but with no luck. oVirt ver: 4.2.8.2-1.el7 Any one can help, please? Best regards. -- Atenciosamente, Kalil de A. Carvalho

2 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3634 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-40p3c.

1 0

[CQ]: 96986, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96986,17 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (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 97775,2 (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://gerrit.ovirt.org/#/c/96986/17 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12980/

1 0

[CQ]: 4d1eb83 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 4d1eb83 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 52f05b8 (ovirt-ansible- hosted-engine-setup) 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 52f05b8 (ovirt-ansible-hosted- engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/4d1eb83a0… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/52f05b8d7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12976/

1 0

[CQ]: 07c7fd2 (ovirt-web-ui) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 07c7fd2 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/07c7fd24e2ae3d824a60a6951ceb97… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3899/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3631 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-v40m2.

1 0

[CQ]: 97819,1 (ovirt-host) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 97819,1 (ovirt-host) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97819/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12972/

1 0

[CQ]: 96984, 18 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96984,18 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (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 97775,2 (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://gerrit.ovirt.org/#/c/96984/18 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12968/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3629 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-qlwpj.

1 0

[CQ]: 96980, 17 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 96980,17 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (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 97775,2 (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://gerrit.ovirt.org/#/c/96980/17 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12964/

1 0

[CQ]: 7f83b03 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 7f83b03 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 52f05b8 (ovirt-ansible- hosted-engine-setup) 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 52f05b8 (ovirt-ansible-hosted- engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/7f83b03f8… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/52f05b8d7… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12960/

1 0

[CQ]: 97729,7 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 18 Feb '19

18 Feb '19

Change 97729,7 (cockpit-ovirt) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97729/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12956/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #1326 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-6tqnq.

1 0

[CQ]: 97257, 24 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Feb '19

18 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97257,24 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97775,2 (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 97775,2 (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://gerrit.ovirt.org/#/c/97257/24 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97775/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12952/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3625 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-xffw9.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 18 Feb '19

18 Feb '19

Failed to run project_setup.sh for: #3625 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-g2dqn.

1 0