- Infra - oVirt List Archives

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

09 Oct '19

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

1 0

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

09 Oct '19

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

1 0

[CQ]: 103257, 5 (ovirt-guest-agent) failed "ovirt-master" system tests
by oVirt Jenkins 09 Oct '19

09 Oct '19

Change 103257,5 (ovirt-guest-agent) 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/103257/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16411/

1 0

[CQ]: 103983,3 (safelease) failed "ovirt-master" system tests
by oVirt Jenkins 09 Oct '19

09 Oct '19

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

1 0

Please remove 4.2 from your stdci.yaml files
by Dafna Ron 09 Oct '19

09 Oct '19

Hi, We have several unstable jobs which are caused because 4.2 is no longer available for CQ. Please remove 4.2 from your stdci.yaml files to avoid getting unstable jobs. Thanks, Dafna

2 2

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

09 Oct '19

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

1 0

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

09 Oct '19

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

1 0

[CQ]: 103387, 8 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Oct '19

09 Oct '19

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

1 0

[CQ]: 103369, 13 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Oct '19

09 Oct '19

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

1 0

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

09 Oct '19

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

1 0

Add Email to github whitelist
by Ritesh Chikatwar 09 Oct '19

09 Oct '19

Please add my email id to whitelist which will help to CI jobs to run whenever a new patch sent by me. Regards Ritesh Chikatwar

2 3

[CQ]: 103368,9 (ovirt-provider-ovn) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 Oct '19

09 Oct '19

Change 103368,9 (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/103368/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2248/

1 0

[CQ]: 103791,6 (ioprocess) failed "ovirt-master" system tests
by oVirt Jenkins 09 Oct '19

09 Oct '19

Change 103791,6 (ioprocess) 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/103791/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16392/

1 0

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

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

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 08 Oct '19

08 Oct '19

Failed to run project_setup.sh for: #1479 ovirt-imageio [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 vm0094.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt
by Michal Skrivanek (oVirt JIRA) 08 Oct '19

08 Oct '19

Michal Skrivanek created OVIRT-2812: --------------------------------------- Summary: move Douglas' rhvanalyzer repo under oVirt Key: OVIRT-2812 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2812 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[CQ]: 103930, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 08 Oct '19

08 Oct '19

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

1 0

[CQ]: a7ab5b0 (ovirt-ansible-vm-infra) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Oct '19

08 Oct '19

A system test invoked by the "ovirt-master" change queue including change a7ab5b0 (ovirt-ansible-vm-infra) failed. However, this change seems not to be the root cause for this failure. Change 4e4aca6 (ovirt-ansible-vm-infra) 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 4e4aca6 (ovirt-ansible-vm- infra) 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-vm-infra/commit/a7ab5b0ee8703f61709a… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/4e4aca6f3c3b2f124da9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16385/

1 0

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

08 Oct '19

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

1 0

[CQ]: a7ab5b0 (ovirt-ansible-vm-infra) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Oct '19

08 Oct '19

A system test invoked by the "ovirt-4.3" change queue including change a7ab5b0 (ovirt-ansible-vm-infra) failed. However, this change seems not to be the root cause for this failure. Change 4e4aca6 (ovirt-ansible-vm-infra) 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 4e4aca6 (ovirt-ansible-vm- infra) 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-vm-infra/commit/a7ab5b0ee8703f61709a… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-vm-infra/commit/4e4aca6f3c3b2f124da9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2243/

1 0

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

08 Oct '19

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

1 0

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

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

1 0

[CQ]: 103257, 5 (ovirt-guest-agent) failed "ovirt-master" system tests
by oVirt Jenkins 08 Oct '19

08 Oct '19

Change 103257,5 (ovirt-guest-agent) 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/103257/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16376/

1 0

[CQ]: 102952, 4 (ovirt-release) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Oct '19

07 Oct '19

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

1 0

[CQ]: 103923, 1 (ovirt-release) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Oct '19

07 Oct '19

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

1 0

[CQ]: 103903, 2 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Oct '19

07 Oct '19

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

1 0

[CQ]: 103240, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Oct '19

07 Oct '19

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

1 0

[CQ]: 103900,1 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 07 Oct '19

07 Oct '19

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

1 0

[JIRA] (OVIRT-2811) s390x tests failing on trying to use `sudo` during artifact collection
by Barak Korren (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2811: ----------------------------------- Assignee: Barak Korren (was: infra) > s390x tests failing on trying to use `sudo` during artifact collection > ---------------------------------------------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves, mock_runner > Reporter: Sandro Bonazzola > Assignee: Barak Korren > Priority: High > Labels: s390x > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on trying to use `sudo` during artifact collection
by Barak Korren (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2811: -------------------------------- Summary: s390x tests failing on trying to use `sudo` during artifact collection (was: s390x tests failing on missing tty) > s390x tests failing on trying to use `sudo` during artifact collection > ---------------------------------------------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves, mock_runner > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > Labels: s390x > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Barak Korren (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2811: -------------------------------- Issue Type: Outage (was: By-EMAIL) > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Slaves, mock_runner > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > Labels: s390x > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Barak Korren (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2811: -------------------------------- Labels: s390x (was: ) > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves, mock_runner > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > Labels: s390x > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Barak Korren (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2811: -------------------------------- Components: Jenkins Slaves mock_runner > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves, mock_runner > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Barak Korren (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2811: ------------------------------------- Root cause of the issue is {{mock}} generating its log files with root permissions, whule it used to generated then with an unprivileged user before. This (fixed) issue seems related: https://github.com/rpm-software-management/mock/issues/322 > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

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

07 Oct '19

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

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Eyal Edri (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2811: ---------------------------------- according to [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] this will later fail on git clone since the logs are root owned. > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Sandro Bonazzola (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Sandro Bonazzola commented on OVIRT-2811: ----------------------------------------- Proposed workaround: [https://gerrit.ovirt.org/103935|https://gerrit.ovirt.org/103935] > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Sandro Bonazzola (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Sandro Bonazzola updated OVIRT-2811: ------------------------------------ Flagged: (was: Impediment) > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Sandro Bonazzola (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Sandro Bonazzola updated OVIRT-2811: ------------------------------------ Flagged: Impediment > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Sandro Bonazzola (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Sandro Bonazzola updated OVIRT-2811: ------------------------------------ Priority: High (was: Medium) > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > Priority: High > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Sandro Bonazzola (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Sandro Bonazzola commented on OVIRT-2811: ----------------------------------------- Il giorno lun 7 ott 2019 alle ore 14:56 Eyal Edri <eedri(a)redhat.com> ha scritto: > I don't think you need use sudo, since you're already root on the mock. > Did you try running without sudo? > I'm not using sudo in check patch script, it's used by CI underlying scripts. > > If you want to use sudo, you'll need to edit the /etc/suders files before > and enable tty. > > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Sandro Bonazzola (oVirt JIRA) 07 Oct '19

07 Oct '19

Sandro Bonazzola created OVIRT-2811: --------------------------------------- Summary: s390x tests failing on missing tty Key: OVIRT-2811 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Sandro Bonazzola Assignee: infra Jenkins is failing on s390x with: [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

3 2

[JIRA] (OVIRT-2811) s390x tests failing on missing tty
by Eyal Edri (oVirt JIRA) 07 Oct '19

07 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2811?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2811: ---------------------------------- I don't think you need use sudo, since you're already root on the mock. Did you try running without sudo? If you want to use sudo, you'll need to edit the /etc/suders files before and enable tty. > s390x tests failing on missing tty > ---------------------------------- > > Key: OVIRT-2811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2811 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: infra > > Jenkins is failing on s390x with: > [2019-10-07T11:45:31.272Z] + sudo -n chown -R ovirt:ovirt > /home/ovirt/workspace/ovirt-release_standard-check-patch/check-patch.fc30.s390x > [2019-10-07T11:45:31.272Z] sudo: sorry, you must have a tty to run sudo > https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-release_standard… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://www.redhat.com/>*Red Hat respects your work life balance. > Therefore there is no need to answer this email out of your office hours.* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

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

07 Oct '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 215 - Failure!
by jenkins＠jenkins.phx.ovirt.org 07 Oct '19

07 Oct '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/215/ Build Number: 215 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #215 [jenkins CI] Auto create ovirt-master ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.ha_recovery_43 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running f2025ba8 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2 lago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 returned with 0 lago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 output: 12277 lago.ssh: DEBUG: start task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running f3098e9a on lago-compat-4-3-suite-master-host-0: kill -KILL 12277 lago.ssh: DEBUG: Command f3098e9a on lago-compat-4-3-suite-master-host-0 returned with 0 --------------------- >> 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/004_basic_sanity.py", line 725, in ha_recovery lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:307b58b9-0d1c-4736-bfab-1425a88c82e3:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running f2025ba8 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2\nlago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 returned with 0\nlago.ssh: DEBUG: Command f2025ba8 on lago-compat-4-3-suite-master-host-0 output:\n 12277\n\nlago.ssh: DEBUG: start task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:db14e219-7ae5-4dc4-95d1-0d4097ed440f:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running f3098e9a on lago-compat-4-3-suite-master-host-0: kill -KILL 12277\n\nlago.ssh: DEBUG: Command f3098e9a on lago-compat-4-3-suite-master-host-0 returned with 0\n--------------------- >> end captured logging << ---------------------'

1 1

[CQ]: 103906,1 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 07 Oct '19

07 Oct '19

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

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #50 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 07 Oct '19

07 Oct '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/50/ Build Name: #50 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 970
by jenkins＠jenkins.phx.ovirt.org 07 Oct '19

07 Oct '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/970//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2810) CI build error with: hudson.plugins.git.GitException: Failed to fetch from https://gerrit.ovirt.org/jenkins
by Barak Korren (oVirt JIRA) 06 Oct '19

06 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2810?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2810: ----------------------------------- Assignee: Barak Korren (was: infra) > CI build error with: hudson.plugins.git.GitException: Failed to fetch from https://gerrit.ovirt.org/jenkins > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2810 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2810 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Master > Reporter: Nir Soffer > Assignee: Barak Korren > > Any imageio patch fail now with the error bellow. > Examples: > *https://gerrit.ovirt.org/q/topic:py3+is:open+project:ovirt-imageio > <https://gerrit.ovirt.org/q/topic:py3+is:open+project:ovirt-imageio>* > *00:07:26* ERROR: Error fetching remote repo 'origin' > *00:07:26* hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/jenkins*00:07:26* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894)*00:07:26* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)*00:07:26* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)*00:07:26* > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)*00:07:26* > at java.util.concurrent.FutureTask.run(FutureTask.java:266)*00:07:26* > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)*00:07:26* > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)*00:07:26* > at java.lang.Thread.run(Thread.java:748)*00:07:26* Caused by: > hudson.plugins.git.GitException: Command "git fetch --tags --progress > https://gerrit.ovirt.org/jenkins > +133b1a1729ce5c6caf1745ad8034ceaa4dd187c5:myhead" returned status code > 128:*00:07:26* stdout: *00:07:26* stderr: error: no such remote ref > 133b1a1729ce5c6caf1745ad8034ceaa4dd187c5*00:07:26* *00:07:26* at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)*00:07:26* > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)*00:07:26* > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)*00:07:26* > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)*00:07:26* > at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)*00:07:26* > at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)*00:07:26* > at hudson.remoting.UserRequest.perform(UserRequest.java:212)*00:07:26* > at hudson.remoting.UserRequest.perform(UserRequest.java:54)*00:07:26* > at hudson.remoting.Request$2.run(Request.java:369)*00:07:26* at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)*00:07:26* > ... 4 more*00:07:26* Suppressed: > hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0008.workers-phx.ovirt.org*00:07:26* at > hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)*00:07:26* > at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)*00:07:26* > at hudson.remoting.Channel.call(Channel.java:957)*00:07:26* at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)*00:07:26* > at sun.reflect.GeneratedMethodAccessor715.invoke(Unknown > Source)*00:07:26* at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*00:07:26* > at java.lang.reflect.Method.invoke(Method.java:498)*00:07:26* at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)*00:07:26* > at com.sun.proxy.$Proxy83.execute(Unknown Source)*00:07:26* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892)*00:07:26* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)*00:07:26* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)*00:07:26* > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)*00:07:26* > ... 4 more[Pipeline] // node -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[JIRA] (OVIRT-2810) CI build error with: hudson.plugins.git.GitException: Failed to fetch from https://gerrit.ovirt.org/jenkins
by Barak Korren (oVirt JIRA) 06 Oct '19

06 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2810?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2810: -------------------------------- Issue Type: Outage (was: By-EMAIL) > CI build error with: hudson.plugins.git.GitException: Failed to fetch from https://gerrit.ovirt.org/jenkins > ----------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2810 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2810 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Jenkins Master > Reporter: Nir Soffer > Assignee: infra > > Any imageio patch fail now with the error bellow. > Examples: > *https://gerrit.ovirt.org/q/topic:py3+is:open+project:ovirt-imageio > <https://gerrit.ovirt.org/q/topic:py3+is:open+project:ovirt-imageio>* > *00:07:26* ERROR: Error fetching remote repo 'origin' > *00:07:26* hudson.plugins.git.GitException: Failed to fetch from > https://gerrit.ovirt.org/jenkins*00:07:26* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:894)*00:07:26* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)*00:07:26* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)*00:07:26* > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)*00:07:26* > at java.util.concurrent.FutureTask.run(FutureTask.java:266)*00:07:26* > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)*00:07:26* > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)*00:07:26* > at java.lang.Thread.run(Thread.java:748)*00:07:26* Caused by: > hudson.plugins.git.GitException: Command "git fetch --tags --progress > https://gerrit.ovirt.org/jenkins > +133b1a1729ce5c6caf1745ad8034ceaa4dd187c5:myhead" returned status code > 128:*00:07:26* stdout: *00:07:26* stderr: error: no such remote ref > 133b1a1729ce5c6caf1745ad8034ceaa4dd187c5*00:07:26* *00:07:26* at > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)*00:07:26* > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)*00:07:26* > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)*00:07:26* > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)*00:07:26* > at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)*00:07:26* > at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)*00:07:26* > at hudson.remoting.UserRequest.perform(UserRequest.java:212)*00:07:26* > at hudson.remoting.UserRequest.perform(UserRequest.java:54)*00:07:26* > at hudson.remoting.Request$2.run(Request.java:369)*00:07:26* at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)*00:07:26* > ... 4 more*00:07:26* Suppressed: > hudson.remoting.Channel$CallSiteStackTrace: Remote call to > vm0008.workers-phx.ovirt.org*00:07:26* at > hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)*00:07:26* > at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)*00:07:26* > at hudson.remoting.Channel.call(Channel.java:957)*00:07:26* at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)*00:07:26* > at sun.reflect.GeneratedMethodAccessor715.invoke(Unknown > Source)*00:07:26* at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*00:07:26* > at java.lang.reflect.Method.invoke(Method.java:498)*00:07:26* at > org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)*00:07:26* > at com.sun.proxy.$Proxy83.execute(Unknown Source)*00:07:26* at > hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892)*00:07:26* at > hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)*00:07:26* > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)*00:07:26* > at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)*00:07:26* > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)*00:07:26* > ... 4 more[Pipeline] // node -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0