- Infra - oVirt List Archives

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

24 Aug '17

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

1 0

[CQ]: 80055, 30 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Aug '17

24 Aug '17

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

1 0

[CQ]: 80003, 30 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Aug '17

24 Aug '17

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

1 0

[CQ]: 79323, 34 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Aug '17

24 Aug '17

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

1 0

[CQ]: 80801, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 24 Aug '17

24 Aug '17

Change 80801,2 (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/80801/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1969/

1 0

[JIRA] (OVIRT-1607) Failed ovirt-system-tests_master_check-patch-el7-x86_64
by Evgheni Dereveanchin (oVirt JIRA) 24 Aug '17

24 Aug '17

This is a multi-part message in MIME format... ------------=_1503580487-31461-340 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D34= 785#comment-34785 ]=20 Evgheni Dereveanchin commented on OVIRT-1607: --------------------------------------------- Interesting, in this particular case it doesn't look like a DNS issue. The = connection was as follows: wget -> proxy01.phx.ovirt.org -> jenkins.ovirt.org Wget was able to access the proxy and the proxy tried to fetch the URL but = got a 404 error from jenkins: 1503475892.751 4 66.187.230.21 TCP_MISS/404 878 GET http://jenkins.ovi= rt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//artifact/export= ed-artifacts/ - HIER_DIRECT/66.187.230.92 text/html I get a 404 error when accessing this URL as well so there's some error in = the fetching script: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6= 4//artifact/exported-artifacts/ [~ngoldin(a)redhat.com] why are we not appending the artifact name or build n= umber to the URL above? In squid logs I see a successful fetch of the Appli= ance via the proxy with a correct URL: 1503475797.567 9880 66.187.230.21 TCP_REFRESH_UNMODIFIED/200 822060496 GE= T http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x= 86_64/524/artifact/exported-artifacts/oVirt-Engine-Appliance-CentOS-x86_64-= 7-20170822.ova - HIER_DIRECT/66.187.230.92 application/octet-stream This one has both a build number and file name and should be added here. > Failed ovirt-system-tests_master_check-patch-el7-x86_64 > ------------------------------------------------------- > > Key: OVIRT-1607 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > I want to verify [1]. It (expectedly) failed in the past, needed [2]. > [2] was merged yesterday and [1] still fails. I retriggered it several > times, and it failed due to different reasons. Last was [3]: > 08:11:38 + find /dev/shm/ost/deployment-image-ng-suite-master -type f > '(' -iname 'nose*.xml' -o -iname '*.junit.xml' ')' -exec mv '{}' > exported-artifacts/ ';' > 08:11:38 find: =EF=BF=BD=EF=BF=BD=EF=BF=BD/dev/shm/ost/deployment-image-n= g-suite-master=EF=BF=BD=EF=BF=BD=EF=BF=BD: No > such file or directory > Please have a look. Thanks, > [1] https://gerrit.ovirt.org/80820 > [2] https://gerrit.ovirt.org/79345 > [3] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el= 7-x86_64/1467/ > --=20 > Didi -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1503580487-31461-340 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D34785#comment-34785 ]</pre> <h3>Evgheni Dereveanchin commented on OVIRT-1607:</h3> <p>Interesting, in this particular case it doesn't look like a DNS issue. T= he connection was as follows: wget -> proxy01.phx.ovirt.org -> jenkin= s.ovirt.org</p> <p>Wget was able to access the proxy and the proxy tried to fetch the URL b= ut got a 404 error from jenkins:</p> <p>1503475892.751 4 66.187.230.21 TCP_MISS/404 878 GET <a href=3D"http= ://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//a= rtifact/exported-artifacts/">http://jenkins.ovirt.org/job/ovirt-node-ng_mas= ter_build-artifacts-el7-x86_64//artifact/exported-artifacts/</a> – HI= ER_DIRECT/66.187.230.92 text/html</p> <p>I get a 404 error when accessing this URL as well so there's some error = in the fetching script: <a href=3D"http://jenkins.ovirt.org/job/ovirt-node-= ng_master_build-artifacts-el7-x86_64//artifact/exported-artifacts/">http://= jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//arti= fact/exported-artifacts/</a></p> <p>[~ngoldin(a)redhat.com] why are we not appending the artifact name or buil= d number to the URL above? In squid logs I see a successful fetch of the Ap= pliance via the proxy with a correct URL:</p> <p>1503475797.567 9880 66.187.230.21 TCP_REFRESH_UNMODIFIED/200 822060496= GET <a href=3D"http://jenkins.ovirt.org/job/ovirt-appliance_master_build-a= rtifacts-el7-x86_64/524/artifact/exported-artifacts/oVirt-Engine-Appliance-= CentOS-x86_64-7-20170822.ova">http://jenkins.ovirt.org/job/ovirt-appliance_= master_build-artifacts-el7-x86_64/524/artifact/exported-artifacts/oVirt-Eng= ine-Appliance-CentOS-x86_64-7-20170822.ova</a> – HIER_DIRECT/66.187.2= 30.92 application/octet-stream</p> <p>This one has both a build number and file name and should be added here.= </p> <blockquote><h3>Failed ovirt-system-tests_master_check-patch-el7-x86_64</h3> <pre> Key: OVIRT-1607 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> <p>I want to verify [1]. It (expectedly) failed in the past, needed [2]. [2= ] was merged yesterday and [1] still fails. I retriggered it several times,= and it failed due to different reasons. Last was [3]: 08:11:38 + find /dev= /shm/ost/deployment-image-ng-suite-master -type f ‘(’ -iname &l= squo;nose*.xml’ -o -iname ‘*.junit.xml’ ‘)’ -= exec mv ‘{}’ exported-artifacts/ ‘;’ 08:11:38 find:= =EF=BF=BD=EF=BF=BD=EF=BF=BD/dev/shm/ost/deployment-image-ng-suite-master= =EF=BF=BD=EF=BF=BD=EF=BF=BD: No such file or directory Please have a look. = Thanks, [1] <a href=3D"https://gerrit.ovirt.org/80820">https://gerrit.ovirt= .org/80820</a> [2] <a href=3D"https://gerrit.ovirt.org/79345">https://gerri= t.ovirt.org/79345</a> [3] <a href=3D"http://jenkins.ovirt.org/job/ovirt-sys= tem-tests_master_check-patch-el7-x86_64/1467/">http://jenkins.ovirt.org/job= /ovirt-system-tests_master_check-patch-el7-x86_64/1467/</a> — Didi</p= ></blockquote> <p>— This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#1000= 59)</p> <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BCmpYLyzYS3r1Q939T2sgz1L1GoZCem-2BYGvNGHDOX5Gk2XiIHy9v060CKZXYqKmpwU8= Pkaaw4w6CPeroyHMrmIBvFxT0L6iKUFlLKdeAV7pVf0DTdPQJ15hrqfBqEgDRtdLKZXHVHDUvGR= V2Kci2CNEK7jTa6rG3BLLFyLVeViSu4llftukeA-2FKJHjgdXm1f-2F5Ff5inQRJrs4cIKoV21y= Uw-3D" alt=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"height:1px != important;width:1px !important;border-width:0 !important;margin-top:0 !impo= rtant;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !i= mportant;padding-top:0 !important;padding-bottom:0 !important;padding-right= :0 !important;padding-left:0 !important;"/> </body></html> ------------=_1503580487-31461-340--

1 0

[JIRA] (OVIRT-1607) Failed ovirt-system-tests_master_check-patch-el7-x86_64
by Anton Marchukov (oVirt JIRA) 24 Aug '17

24 Aug '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-1607: ---------------------------------------- There are some occasional flaky DNS stuff going on. But this job has other problems since DNS is not that flaky. > Failed ovirt-system-tests_master_check-patch-el7-x86_64 > ------------------------------------------------------- > > Key: OVIRT-1607 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > I want to verify [1]. It (expectedly) failed in the past, needed [2]. > [2] was merged yesterday and [1] still fails. I retriggered it several > times, and it failed due to different reasons. Last was [3]: > 08:11:38 + find /dev/shm/ost/deployment-image-ng-suite-master -type f > '(' -iname 'nose*.xml' -o -iname '*.junit.xml' ')' -exec mv '{}' > exported-artifacts/ ';' > 08:11:38 find: ��/dev/shm/ost/deployment-image-ng-suite-master��: No > such file or directory > Please have a look. Thanks, > [1] https://gerrit.ovirt.org/80820 > [2] https://gerrit.ovirt.org/79345 > [3] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… > -- > Didi -- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 340 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Aug '17

24 Aug '17

------=_Part_255_1424246264.1503571973678 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 340 Build Status: Failure Triggered By: Started by user Lev Veyde ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #340 [Yuval Turgeman] nodectl: fixed typo in overall status check ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_255_1424246264.1503571973678--

1 1

[CQ]: 80825,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 24 Aug '17

24 Aug '17

Change 80825,3 (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/80825/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1961/

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 232 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Aug '17

24 Aug '17

------=_Part_231_1919252347.1503548130900 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-snapshot_build-artifac… Build Number: 232 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #232 [Daniel Belenky] mock_runner fix empty mrmap bug [Ryan Barry] Bump version ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_231_1919252347.1503548130900--

1 1