- Infra - oVirt List Archives

[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