- Infra - oVirt List Archives

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 13 May '19

13 May '19

Failed to run project_setup.sh for: #2471 jenkins [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 vm0221.workers-phx.ovirt.org.

1 0

ovrit hyperconverged replicas
by rt.tarantino＠gmail.com 13 May '19

13 May '19

Hello is it possible to have a replica 4 or greater gluster with hyperconverged ovirt?

1 0

[JIRA] (OVIRT-2726) Upgrade hyperkitty to 1.2.2
by Anton Marchukov (oVirt JIRA) 13 May '19

13 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2726?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2726: -------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Upgrade hyperkitty to 1.2.2 > --------------------------- > > Key: OVIRT-2726 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2726 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Marc Dequènes (Duck) > > We are currently running hyperkitty 1.1.5 (which seems not being released > by the developers), latest one is 1.2.2.It introduces a few featrue and > support for newer django. > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> > <https://redhat.com/summit> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2726) Upgrade hyperkitty to 1.2.2
by sbonazzo (oVirt JIRA) 13 May '19

13 May '19

sbonazzo created OVIRT-2726: ------------------------------- Summary: Upgrade hyperkitty to 1.2.2 Key: OVIRT-2726 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2726 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra We are currently running hyperkitty 1.1.5 (which seems not being released by the developers), latest one is 1.2.2.It introduces a few featrue and support for newer django. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Eyal Edri (oVirt JIRA) 13 May '19

13 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2725: ---------------------------------- I fixed it yesterday by cleaning up the slave, anyone can do with the commands written in the FAQ doc. What we need to add is a cleanup script that will do it on a regular basis ( 2 lines of bash ): (after you login to the VM) with sudo: mock -r ./fedora-28-s390x.cfg --shell rm rfv /hostvar/cache/mock/fedora??s390x* > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Dafna Ron (oVirt JIRA) 13 May '19

13 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2725: ---------------------------------- The build that failed is fc28.x390: 15:52:20 Running on lfedora1.lf-dev.marist.edu in /home/ovirt/workspace/standard-manual-runner Agent lfedora1.lf-dev.marist.edu (lfedora1.lf-dev.marist.edu s390x loaned VM) [~ederevea] can you please take a look? > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

oVirt infra daily report - unstable production jobs - 823
by jenkins＠jenkins.phx.ovirt.org 12 May '19

12 May '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/823//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2725: ----------------------------------- On Sun, May 12, 2019 at 8:00 PM Eyal Edri <eedri(a)redhat.com> wrote: > You s390x build is failing, its the only VM we have. > I cleaned up the space there. it should work now. > It works now: http://jenkins.ovirt.org/job/standard-manual-runner/250/ I think we had issues with the s390x slave in the past. I guess this will bite us again in 2-3 months. > > On Sun, May 12, 2019 at 6:44 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Sun, May 12, 2019 at 6:32 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >>> On Sun, May 12, 2019 at 6:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >>> >>>> I had this failure in yum install: >>>> >>>> [2019-05-12T14:54:55.706Z] Error Summary >>>> [2019-05-12T14:54:55.706Z] ------------- >>>> [2019-05-12T14:54:55.706Z] Disk Requirements: >>>> [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / >>>> filesystem. >>>> >>>> Build: >>>> >>>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >>>> >>>> Trying build again, hopefully will get a slave with more space... >>>> >>> >>> Unfortunately, I got the same slave again: >>> >>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >>> >> >> Another failure: >> https://jenkins.ovirt.org/job/standard-manual-runner/249/ >> >> >>> >>> This blocks urgent bug: >>> https://bugzilla.redhat.com/1700623 >>> >>> Nir >>> >>> >>> >>>> >>>> Nir >>>> >>> > > -- > > Eyal edri > > > MANAGER > > CONTINUOUS PRODUCTIZATION > > SYSTEM ENGINEERING > > Red Hat <https://www.redhat.com/> > <https://red.ht/sig> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) > > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2725: ----------------------------------- Thanks, trying again. > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2725: ----------------------------------- On Sun, May 12, 2019 at 6:32 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, May 12, 2019 at 6:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> I had this failure in yum install: >> >> [2019-05-12T14:54:55.706Z] Error Summary >> [2019-05-12T14:54:55.706Z] ------------- >> [2019-05-12T14:54:55.706Z] Disk Requirements: >> [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / >> filesystem. >> >> Build: >> >> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >> >> Trying build again, hopefully will get a slave with more space... >> > > Unfortunately, I got the same slave again: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Another failure: https://jenkins.ovirt.org/job/standard-manual-runner/249/ > > This blocks urgent bug: > https://bugzilla.redhat.com/1700623 > > Nir > > > >> >> Nir >> > > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

3 2

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Eyal Edri (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2725: ---------------------------------- You s390x build is failing, its the only VM we have. I cleaned up the space there. it should work now. On Sun, May 12, 2019 at 6:44 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, May 12, 2019 at 6:32 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Sun, May 12, 2019 at 6:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >>> I had this failure in yum install: >>> >>> [2019-05-12T14:54:55.706Z] Error Summary >>> [2019-05-12T14:54:55.706Z] ------------- >>> [2019-05-12T14:54:55.706Z] Disk Requirements: >>> [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / >>> filesystem. >>> >>> Build: >>> >>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >>> >>> Trying build again, hopefully will get a slave with more space... >>> >> >> Unfortunately, I got the same slave again: >> >> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >> > > Another failure: > https://jenkins.ovirt.org/job/standard-manual-runner/249/ > > >> >> This blocks urgent bug: >> https://bugzilla.redhat.com/1700623 >> >> Nir >> >> >> >>> >>> Nir >>> >> -- Eyal edri MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Eyal Edri (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2725: ---------------------------------- I cleaned up the slave using: mock -r ./fedora-28-s390x.cfg --shell rm -rfv /hostvar/cache/mock/fedora-??-s390x-* I think this slave isn't cleaned up because we don't have sudo on it. perhaps a local cleanup script can help. On Sun, May 12, 2019 at 6:46 PM Nir Soffer (oVirt JIRA) < -- Eyal edri MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2725: ----------------------------------- On Sun, May 12, 2019 at 6:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > I had this failure in yum install: > > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > > Build: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > Trying build again, hopefully will get a slave with more space... > Unfortunately, I got the same slave again: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… This blocks urgent bug: https://bugzilla.redhat.com/1700623 Nir > > Nir > > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

Nir Soffer created OVIRT-2725: --------------------------------- Summary: Build artifacts failed - not enough free space on file system Key: OVIRT-2725 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I had this failure in yum install: [2019-05-12T14:54:55.706Z] Error Summary [2019-05-12T14:54:55.706Z] ------------- [2019-05-12T14:54:55.706Z] Disk Requirements: [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / filesystem. Build: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Trying build again, hopefully will get a slave with more space... Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 May '19

12 May '19

Change 99533,1 (ovirt-vmconsole) 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://gerrit.ovirt.org/#/c/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4323/

4 5

oVirt infra daily report - unstable production jobs - 822
by jenkins＠jenkins.phx.ovirt.org 11 May '19

11 May '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/822//artifact/exported-a… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 821
by jenkins＠jenkins.phx.ovirt.org 10 May '19

10 May '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/821//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 May '19

10 May '19

Change 99533,1 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/849/

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 10-05-2019 ] [ 004_basic_sanity.vm_run ]
by Dafna Ron 10 May '19

10 May '19

Hi, We are failing upgrade-from-release-suite.el7.x86_64 / 004_basic_sanity.vm_run The issue is an unexpected exception in vdsm. root cause based on CQ is this patch: https://gerrit.ovirt.org/#/c/99854/ - yum: Allow downloading only 'vdsm' package Logs can be found here: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14079/artifac… Marcin, can you please take a look? error: vdsm: 2019-05-10 05:06:38,329-0400 ERROR (jsonrpc/0) [api] FINISH create error=Unexpected exception (api:131) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 124, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 245, in create raise exception.UnexpectedError() UnexpectedError: Unexpected exception 2019-05-10 05:06:38,330-0400 INFO (jsonrpc/0) [api.virt] FINISH create return={'status': {'message': 'Unexpected exception', 'code': 16}} from=::ffff:192.168.201.2,39486, flow_id=83e4f0c4-a39a-45aa-891f-4022765e1a87, vmId=397013a0-b7d4-4d38-86c3-e944cebd75a7 (api:54) 2019-05-10 05:06:38,331-0400 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call VM.create failed (error 16) in 0.00 seconds (__init__:312) 2019-05-10 05:06:38,629-0400 INFO (jsonrpc/7) [vdsm.api] FINISH getStorageDomainInfo return={'info': {'uuid': '24498263-8985-46a9-9161-f65ee776cb7f', 'vgMetadataDevice': '360014051f333158820a4cc6ab3be5b55', 'vguuid': 'rXTLNc-JwEz-0dtL-Z2EC-ASqn-gzkg-jDJa1b', 'metadataDevice': '360014051f333158820a4cc6ab3be5b55', 'state': 'OK', 'version': '4', 'role': 'Master', 'type': 'ISCSI', 'class': 'Data', 'pool': ['3e330122-c587-4078-b9a4-13dbb697c5cc'], 'name': 'iscsi'}} from=::ffff:192.168.201.2,39486, flow_id=3f76d32a, task_id=084e7ee5-3c43-4905-833f-9a522043a862 (api:54) engine: 2019-05-10 05:06:38,328-04 ERROR [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] VDS::create Failed creating vm 'v m0' in vds = '566eda0f-3ef0-4791-a618-1e649af4b0be' error = 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to C reateBrokerVDS, error = Unexpected exception, code = 16' 2019-05-10 05:06:38,328-04 INFO [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] FINISH, CreateVDSCommand, return: Down, log id: 3cb7c62d 2019-05-10 05:06:38,328-04 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Failed to run VM 'vm0': EngineException: or g.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to CreateBrokerVDS, error = Unexpected exception, code = 16 (Failed with error unexpected and code 16) 2019-05-10 05:06:38,328-04 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Lock freed to object 'EngineLock:{exclu siveLocks='[397013a0-b7d4-4d38-86c3-e944cebd75a7=VM]', sharedLocks=''}' 2019-05-10 05:06:38,329-04 INFO [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Trying to rerun VM 'vm0' 2019-05-10 05:06:38,373-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] EVENT_ID: USE R_INITIATED_RUN_VM_FAILED(151), Failed to run VM vm0 on Host lago-upgrade-from-release-suite-master-host-0. 2019-05-10 05:06:38,381-04 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Lock Acquired to object 'EngineLock:{ex clusiveLocks='[397013a0-b7d4-4d38-86c3-e944cebd75a7=VM]', sharedLocks=''}' 2019-05-10 05:06:38,393-04 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] START, IsVmDuringIn itiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='397013a0-b7d4-4d38-86c3-e944cebd75a7'}), log id: 96be328 2019-05-10 05:06:38,393-04 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] FINISH, IsVmDuringI nitiatingVDSCommand, return: false, log id: 96be328 2019-05-10 05:06:38,403-04 WARN [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Validation of action 'RunVmOnce' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS 2019-05-10 05:06:38,404-04 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Lock freed to object 'EngineLock:{exclu siveLocks='[397013a0-b7d4-4d38-86c3-e944cebd75a7=VM]', sharedLocks=''}' 2019-05-10 05:06:38,413-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] EVENT_ID: USE R_FAILED_RUN_VM(54), Failed to run VM vm0 (User: admin@internal-authz). 2019-05-10 05:06:38,462-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [There are no hosts to use. Check that the cluster contains at least one host in Up state.] 2019-05-10 05:06:38,466-04 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-35) [3f40b3e8] Running command: ProcessDownVmCommand internal: true. Thanks, Dafna

3 4

Subject: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-05-2019 ] [ upgrade_hosts ]
by Dafna Ron 10 May '19

10 May '19

Hi, We are failing test upgrade_hosts on upgrade-from-release-suite-master. From the logs I can see that we are calling migrate vm when we have only one host and the vm seem to have been shut down before the maintenance call is issued. Can you please look into this? suspected patch reported as root cause by CQ is: https://gerrit.ovirt.org/#/c/98920/ - core: Add MigrateMultipleVms command and use it for host maintenance logs are found here: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14021/artifac… I can see the issue is vm migration when putting host in maintenance: 2019-05-07 06:02:04,170-04 INFO [org.ovirt.engine.core.bll.MaintenanceVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [05592db2-f859-487b-b779-4b32eec5bab 3] Running command: MaintenanceVdsCommand internal: true. Entities affected : ID: 38e1379b-c3b6-4a2e-91df-d1f346e414a9 Type: VDS 2019-05-07 06:02:04,215-04 WARN [org.ovirt.engine.core.bll.MigrateMultipleVmsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [33485140] Validation of action 'MigrateMultipleVms' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VMS_NOT_FOUND 2019-05-07 06:02:04,221-04 ERROR [org.ovirt.engine.core.bll.MaintenanceVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [33485140] Failed to migrate one or more VMs. 2019-05-07 06:02:04,227-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [33485140] EVEN T_ID: VDS_MAINTENANCE_FAILED(17), Failed to switch Host lago-upgrade-from-release-suite-master-host-0 to Maintenance mode. 2019-05-07 06:02:04,239-04 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] Lock Acquired to object 'Eng ineLock:{exclusiveLocks='[38e1379b-c3b6-4a2e-91df-d1f346e414a9=VDS]', sharedLocks=''}' 2019-05-07 06:02:04,242-04 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] Running command: ActivateVds Command internal: true. Entities affected : ID: 38e1379b-c3b6-4a2e-91df-d1f346e414a9 Type: VDSAction group MANIPULATE_HOST with role type ADMIN 2019-05-07 06:02:04,243-04 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] Before acquiring lock in ord er to prevent monitoring for host 'lago-upgrade-from-release-suite-master-host-0' from data-center 'test-dc' 2019-05-07 06:02:04,243-04 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] Lock acquired, from now a mo nitoring of host will be skipped for host 'lago-upgrade-from-release-suite-master-host-0' from data-center 'test-dc' 2019-05-07 06:02:04,252-04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] START, SetVdsStatu sVDSCommand(HostName = lago-upgrade-from-release-suite-master-host-0, SetVdsStatusVDSCommandParameters:{hostId='38e1379b-c3b6-4a2e-91df-d1f346e414a9', status='Unassigned', n onOperationalReason='NONE', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 2c8aa211 2019-05-07 06:02:04,256-04 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] FINISH, SetVdsStat usVDSCommand, return: , log id: 2c8aa211 2019-05-07 06:02:04,261-04 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] Activate host finished. Lock released. Monitoring can run now for host 'lago-upgrade-from-release-suite-master-host-0' from data-center 'test-dc' 2019-05-07 06:02:04,265-04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] EVEN T_ID: VDS_ACTIVATE(16), Activation of host lago-upgrade-from-release-suite-master-host-0 initiated by admin@internal-authz. 2019-05-07 06:02:04,266-04 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [70840477] Lock freed to object 'Engine Lock:{exclusiveLocks='[38e1379b-c3b6-4a2e-91df-d1f346e414a9=VDS]', sharedLocks=''}' 2019-05-07 06:02:04,484-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-96) [05592db2-f859-487b-b779-4b32 eec5bab3] Host 'lago-upgrade-from-release-suite-master-host-0' failed to move to maintenance mode. Upgrade process is terminated. I can see there was only one vm running: drwxrwxr-x. 2 dron dron 1024 May 7 11:49 qemu [dron@dron post-004_basic_sanity.py]$ ls -l lago-upgrade-from-release-suite-master-host-0/_var_log/libvirt/qemu/ total 6 -rw-rw-r--. 1 dron dron 4466 May 7 10:12 vm-with-iface.log and I can see that there was an attempt to terminate it with an error that it does not exist: stroyVmVDSCommandParameters:{hostId='38e1379b-c3b6-4a2e-91df-d1f346e414a9', vmId='dfbd75e2-a9cb-4fca-8788-a16954db4abf', secondsToWait='0', gracefully='false', reason='', ig noreNoVm='false'}), log id: 24278e9b 2019-05-07 06:01:41,082-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (default task-1) [105f7555-517b-4bf9-b86e-6eb42375de20] START, DestroyVDSComma nd(HostName = lago-upgrade-from-release-suite-master-host-0, DestroyVmVDSCommandParameters:{hostId='38e1379b-c3b6-4a2e-91df-d1f346e414a9', vmId='dfbd75e2-a9cb-4fca-8788-a169 54db4abf', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='false'}), log id: 78bba2f8 2019-05-07 06:01:42,090-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (default task-1) [105f7555-517b-4bf9-b86e-6eb42375de20] FINISH, DestroyVDSComm and, return: , log id: 78bba2f8 2019-05-07 06:01:42,090-04 INFO [org.ovirt.engine.core.vdsbroker.DestroyVmVDSCommand] (default task-1) [105f7555-517b-4bf9-b86e-6eb42375de20] FINISH, DestroyVmVDSCommand, r eturn: , log id: 24278e9b 2019-05-07 06:01:42,094-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-4) [] VM 'dfbd75e2-a9cb-4fca-8788-a16954db4abf' was reported as Down on VDS '38e1379b-c3b6-4a2e-91df-d1f346e414a9'(lago-upgrade-from-release-suite-master-host-0) 2019-05-07 06:01:42,096-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-4) [] START, DestroyVDSCommand(HostName = lago-upgrade- from-release-suite-master-host-0, DestroyVmVDSCommandParameters:{hostId='38e1379b-c3b6-4a2e-91df-d1f346e414a9', vmId='dfbd75e2-a9cb-4fca-8788-a16954db4abf', secondsToWait='0 ', gracefully='false', reason='', ignoreNoVm='true'}), log id: 1dbd31eb 2019-05-07 06:01:42,114-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-4) [] Failed to destroy VM 'dfbd75e2-a9cb-4fca-8788-a16 954db4abf' because VM does not exist, ignoring

3 10

[CQ]: 99822, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 May '19

10 May '19

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

1 0

[CQ]: 99822, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 May '19

10 May '19

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

1 0

[CQ]: 99856,2 (ovirt-release) failed "ovirt-master" system tests
by oVirt Jenkins 10 May '19

10 May '19

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

1 0

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

10 May '19

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

1 0

[oVirt Jenkins] ovirt-release_master_build-artifacts-fcraw-x86_64 - Build # 99 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 May '19

10 May '19

Project: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build: http://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-fcraw-x86… Build Number: 99 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #99 [Sandro Bonazzola] fedora: fix dep repo file [Sandro Bonazzola] ovirt-engine-sdk: add fc29 and fcraw jobs on master [Sandro Bonazzola] ovirt-engine-sdk: exclude fcraw for s390 [Sandro Bonazzola] dist: add fedora 30 support ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 99791,2 (mom) failed "ovirt-master" system tests
by oVirt Jenkins 10 May '19

10 May '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 65 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/65/ Build Number: 65 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #65 [Simone Tiraboschi] Add he-basic-role-remote-suite-4.3 [Sandro Bonazzola] fedora: drop fedora 27 usage [Sandro Bonazzola] fedora: drop fedora 27 mirroring [Sandro Bonazzola] ovirt-host: move master to stdci v2 [Sandro Bonazzola] ovirt-vmconsole: add fc29 and fcraw jobs on master [Sandro Bonazzola] ovirt-hosted-engine-setup: drop manual build jobs [Sandro Bonazzola] ovirt-hosted-engine-setup: move master to v2 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 008_basic_ui_sanity.initialize_firefox_43 Error Message: Message: Error forwarding the new session new session request for webdriver should contain a location header or an 'application/json;charset=UTF-8' response body with the session ID. Stacktrace: at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117) at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84) at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68) at javax.servlet.http.HttpServlet.service (HttpServlet.java:707) at javax.servlet.http.HttpServlet.service (HttpServlet.java:790) at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860) at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168) at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473) at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166) at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155) at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141) at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132) at org.seleniumhq.jetty9.server.Server.handle (Server.java:530) at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347) at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256) at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279) at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102) at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131) at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626) at java.lang.Thread.run (Thread.java:748) -------------------- >> begin captured stdout << --------------------- _init_browser, connecting to hub at http://172.18.0.2:4444/wd/hub Message: Error forwarding the new session new session request for webdriver should contain a location header or an 'application/json;charset=UTF-8' response body with the session ID. Stacktrace: at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117) at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84) at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68) at javax.servlet.http.HttpServlet.service (HttpServlet.java:707) at javax.servlet.http.HttpServlet.service (HttpServlet.java:790) at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860) at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168) at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473) at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166) at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155) at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141) at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132) at org.seleniumhq.jetty9.server.Server.handle (Server.java:530) at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347) at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256) at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279) at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102) at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131) at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626) at java.lang.Thread.run (Thread.java:748) WebDriverException in _init_browser connecting to hub --------------------- >> end captured stdout << ---------------------- -------------------- >> begin captured logging << -------------------- selenium.webdriver.remote.remote_connection: DEBUG: POST http://172.18.0.2:4444/wd/hub/session {"capabilities": {"alwaysMatch": {"acceptInsecureCerts": true, "browserName": "firefox", "platformName": "linux", "browserVersion": "58.0.1"}, "firstMatch": [{}]}, "desiredCapabilities": {"acceptInsecureCerts": true, "platform": "LINUX", "browserName": "firefox", "version": "58.0.1", "marionette": true}} urllib3.connectionpool: DEBUG: Starting new HTTP connection (1): 172.18.0.2:4444 urllib3.connectionpool: DEBUG: http://172.18.0.2:4444 "POST /wd/hub/session HTTP/1.1" 500 8055 selenium.webdriver.remote.remote_connection: DEBUG: Finished Request --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/008_basic_ui_sanity.py", line 223, in initialize_firefox _init_driver(_get_firefox_capabilities()) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/008_basic_ui_sanity.py", line 243, in _init_driver raise e 'Message: Error forwarding the new session new session request for webdriver should contain a location header or an \'application/json;charset=UTF-8\' response body with the session ID.\nStacktrace:\n at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117)\n at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84)\n at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:707)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:790)\n at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141)\n at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132)\n at org.seleniumhq.jetty9.server.Server.handle (Server.java:530)\n at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347)\n at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256)\n at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279)\n at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102)\n at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131)\n at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626)\n at java.lang.Thread.run (Thread.java:748)\n-------------------- >> begin captured stdout << ---------------------\n_init_browser, connecting to hub at http://172.18.0.2:4444/wd/hub\nMessage: Error forwarding the new session new session request for webdriver should contain a location header or an \'application/json;charset=UTF-8\' response body with the session ID.\nStacktrace:\n at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117)\n at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84)\n at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:707)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:790)\n at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141)\n at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132)\n at org.seleniumhq.jetty9.server.Server.handle (Server.java:530)\n at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347)\n at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256)\n at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279)\n at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102)\n at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131)\n at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626)\n at java.lang.Thread.run (Thread.java:748)\nWebDriverException in _init_browser connecting to hub\n\n--------------------- >> end captured stdout << ----------------------\n-------------------- >> begin captured logging << --------------------\nselenium.webdriver.remote.remote_connection: DEBUG: POST http://172.18.0.2:4444/wd/hub/session {"capabilities": {"alwaysMatch": {"acceptInsecureCerts": true, "browserName": "firefox", "platformName": "linux", "browserVersion": "58.0.1"}, "firstMatch": [{}]}, "desiredCapabilities": {"acceptInsecureCerts": true, "platform": "LINUX", "browserName": "firefox", "version": "58.0.1", "marionette": true}}\nurllib3.connectionpool: DEBUG: Starting new HTTP connection (1): 172.18.0.2:4444\nurllib3.connectionpool: DEBUG: http://172.18.0.2:4444 "POST /wd/hub/session HTTP/1.1" 500 8055\nselenium.webdriver.remote.remote_connection: DEBUG: Finished Request\n--------------------- >> end captured logging << ---------------------'

1 1

[CQ]: 99854,1 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 09 May '19

09 May '19

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

1 0

oVirt infra daily report - unstable production jobs - 820
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '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/820//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99791,2 (mom) failed "ovirt-4.2" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99791,2 (mom) 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://gerrit.ovirt.org/#/c/99791/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4318/

1 0

[CQ]: 99849,1 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99849,1 (ovirt-provider-ovn) 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://gerrit.ovirt.org/#/c/99849/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4315/

1 0

[CQ]: 99658, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 May '19

09 May '19

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

1 0

[CQ]: 99791,2 (mom) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99791,2 (mom) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99791/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/844/

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '19

Failed to run project_setup.sh for: #5287 vdsm [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 vm0037.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '19

Failed to run project_setup.sh for: #5285 vdsm [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 vm0036.workers-phx.ovirt.org.

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99533,1 (ovirt-vmconsole) 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://gerrit.ovirt.org/#/c/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4311/

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99533,1 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/841/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-opstools-release-el7-x86_64 #415
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-opstools-release-el…> Changes: [Sandro Bonazzola] ovirt-engine-sdk: add fc29 and fcraw jobs on master ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-opstools-release-el…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision f01594aa7c8193347bbeb332369106988bdb6fa2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f01594aa7c8193347bbeb332369106988bdb6fa2 Commit message: "ovirt-engine-sdk: add fc29 and fcraw jobs on master" > git rev-list --no-walk 7393ecb197f40cae659ffa855f71950dfec2eefa # timeout=10 [system-sync_mirrors-centos-opstools-release-el7-x86_64] $ /bin/bash -xe /tmp/jenkins579857252666989871.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-opstools-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-opstools-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-opstools-release-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-opstools-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-opstools-release-el7 yum + local repo_name=centos-opstools-release-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-opstools-release-el7 /var/www/html/repos/yum/centos-opstools-release-el7/base + check_yum_sync_needed centos-opstools-release-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-opstools-release-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-opstools-release-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-opstools-release-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-opstools-release-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-opstools-release-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-opstools-release-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: failure: repodata/411400c3345dd38f426f8baa45925b7c88366226cd79c792e3c9ba8cf01db356-primary.sqlite.bz2 from centos-opstools-release-el7: [Errno 256] No more mirrors to try. http://mirror.centos.org/centos/7/opstools/x86_64/repodata/411400c3345dd38f…: [Errno 14] HTTP Error 404 - Not Found + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 99657, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 May '19

09 May '19

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

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99533,1 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/837/

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99533,1 (ovirt-vmconsole) 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://gerrit.ovirt.org/#/c/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4306/

1 0

[CQ]: 99507, 12 (ovirt-engine-api-explorer) failed "ovirt-master" system tests
by oVirt Jenkins 09 May '19

09 May '19

Change 99507,12 (ovirt-engine-api-explorer) 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/99507/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14058/

1 0

[JIRA] (OVIRT-2722) Jenkins is very slow now - can someone restart it?
by Evgheni Dereveanchin (oVirt JIRA) 09 May '19

09 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2722?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2722: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Jenkins is very slow now - can someone restart it? > -------------------------------------------------- > > Key: OVIRT-2722 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2722 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > $ time curl -s https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ > >/dev/null > real 0m27.380s > user 0m0.038s > sys 0m0.028s > For reference: > $ time curl -s https://travis-ci.org/oVirt/vdsm/builds >/dev/null > real 0m0.614s > user 0m0.027s > sys 0m0.015s > Can someone restart jenkins? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100100)

1 0

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #598
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '19

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/598/display/red…>

1 1

[CQ]: 99746, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 09 May '19

09 May '19

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

1 0

Jenkins build became unstable: ovirt_4.3_publish-rpms_nightly #122
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '19

See <http://jenkins.ovirt.org/job/ovirt_4.3_publish-rpms_nightly/122/display/red…>

1 1

Jenkins build became unstable: ovirt_master_publish-rpms_nightly #1347
by jenkins＠jenkins.phx.ovirt.org 09 May '19

09 May '19

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/1347/display…>

1 1

oVirt infra daily report - unstable production jobs - 819
by jenkins＠jenkins.phx.ovirt.org 08 May '19

08 May '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/819//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99782,3 (ovirt-provider-ovn) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 May '19

08 May '19

Change 99782,3 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99782/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/829/

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 08 May '19

08 May '19

Change 99533,1 (ovirt-vmconsole) 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://gerrit.ovirt.org/#/c/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4297/

2 1