- Infra - oVirt List Archives

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

01 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100404,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 100309,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100309,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100404/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100309/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14375/

1 0

[CQ]: 100079, 1 (ovirt-engine-api-explorer) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '19

31 May '19

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

1 0

[CQ]: 99603, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '19

31 May '19

Change 99603,1 (ovirt-engine-nodejs-modules) 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/99603/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14364/

1 0

[CQ]: 100377, 2 (ovirt-engine-ui-extensions) failed "ovirt-4.3" system tests
by oVirt Jenkins 31 May '19

31 May '19

Change 100377,2 (ovirt-engine-ui-extensions) 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/100377/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1041/

1 0

[oVirt CI] standard-enqueue - Build #21543 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 31 May '19

31 May '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/21543/ Build Name: #21543 Build Description: Gerrit: 99777 - cockpit-ovirt (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/99777 - title: Introduce Vagrant Local Development Environment - project: cockpit-ovirt - branch: master - author: Evgeny Slutsky <>

1 0

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

31 May '19

A system test invoked by the "ovirt-master" change queue including change 100368,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100312,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100312,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100368/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100312/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14358/

1 0

[oVirt CI] standard-enqueue - Build #21535 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 31 May '19

31 May '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/21535/ Build Name: #21535 Build Description: Gerrit: 62940 - ovirt-engine-sdk (master, 3.6, 4.1, 4.2, 4.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/62940 - title: sdk: Prepare for next development iteration - project: ovirt-engine-sdk - branch: sdk_3.6 - author: Juan Hernandez <juan.hernandez(a)redhat.com>

1 0

[CQ]: 100302,2 (ovirt-wgt) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '19

31 May '19

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

1 0

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

31 May '19

A system test invoked by the "ovirt-master" change queue including change 100092,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 100309,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100309,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100092/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100309/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14349/

1 0

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

31 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/841//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 100377, 2 (ovirt-engine-ui-extensions) failed "ovirt-4.3" system tests
by oVirt Jenkins 30 May '19

30 May '19

Change 100377,2 (ovirt-engine-ui-extensions) 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/100377/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1032/

1 0

[JIRA] (OVIRT-2736) Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
by Ehud Yonasi (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2736: ------------------------------------ It fails on installing createrepo package which probably does not exist in fc30. We are working on fixing it. On Thu, May 30, 2019 at 4:05 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > Hi, > On 5/30/19 2:43 PM, Nir Soffer wrote: > > > On Thu, May 30, 2019 at 3:41 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> Here a failed build: >> >> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >> > > Marcin, can it be related to the latest py3 changes? > > Don't really think so - please notice that only s390x agents are touched. > The only thing that changed recently was adding a 'build-artifacts' job > that uses Python 3.6 to build artifacts on s390x machines. > I've recently reported a problem that the agents ran out of space and it > was fixed by Ehud: > > https://ovirt-jira.atlassian.net/browse/OVIRT-2734 > > Ehud, did you notice anything weird occupying disk space on these agents? > > >> >> The second failure today. >> >> I hope we can fix this quickly. >> >> If not we need to disable fedora builds for now. >> > > Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-2736 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Here a failed build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The second failure today. > I hope we can fix this quickly. > If not we need to disable fedora builds for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2736) Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
by Marcin Sobczyk (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jira.… ] Marcin Sobczyk commented on OVIRT-2736: --------------------------------------- Hi, On 5/30/19 2:43 PM, Nir Soffer wrote: > > On Thu, May 30, 2019 at 3:41 PM Nir Soffer <nsoffer(a)redhat.com > <mailto:nsoffer@redhat.com>> wrote: > > Here a failed build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > > Marcin, can it be related to the latest py3 changes? Don't really think so - please notice that only s390x agents are touched. The only thing that changed recently was adding a 'build-artifacts' job that uses Python 3.6 to build artifacts on s390x machines. I've recently reported a problem that the agents ran out of space and it was fixed by Ehud: https://ovirt-jira.atlassian.net/browse/OVIRT-2734 Ehud, did you notice anything weird occupying disk space on these agents? > > > The second failure today. > > I hope we can fix this quickly. > > If not we need to disable fedora builds for now. > > Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-2736 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Here a failed build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The second failure today. > I hope we can fix this quickly. > If not we need to disable fedora builds for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2736) Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
by Nir Soffer (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2736: ----------------------------------- On Thu, May 30, 2019 at 3:45 PM Barak Korren <bkorren(a)redhat.com> wrote: > Please track issues on the ticket you already opened about this and avoid > spreading the information over multiple threads. > > Its the s390x issue I already explained - its running f30 atm which is > causing some trouble because the `createrepo` package was dropped from it. > Thanks, I did not notice this is again s390x, you can close this. > > On Thu, 30 May 2019 at 15:41, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> Here a failed build: >> >> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >> >> The second failure today. >> >> I hope we can fix this quickly. >> >> If not we need to disable fedora builds for now. >> > > > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > > Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-2736 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Here a failed build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The second failure today. > I hope we can fix this quickly. > If not we need to disable fedora builds for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2736) Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
by Barak Korren (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2736: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) Closing - this is a duplicate of OVIRT-2735 > Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-2736 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Here a failed build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The second failure today. > I hope we can fix this quickly. > If not we need to disable fedora builds for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2736) Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
by Barak Korren (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2736: ------------------------------------- Please track issues on the ticket you already opened about this and avoid spreading the information over multiple threads. Its the s390x issue I already explained - its running f30 atm which is causing some trouble because the `createrepo` package was dropped from it. On Thu, 30 May 2019 at 15:41, Nir Soffer <nsoffer(a)redhat.com> wrote: > Here a failed build: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > The second failure today. > > I hope we can fix this quickly. > > If not we need to disable fedora builds for now. > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-2736 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Here a failed build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The second failure today. > I hope we can fix this quickly. > If not we need to disable fedora builds for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2736) Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
by Nir Soffer (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2736: ----------------------------------- On Thu, May 30, 2019 at 3:41 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > Here a failed build: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Marcin, can it be related to the latest py3 changes? > > > The second failure today. > > I hope we can fix this quickly. > > If not we need to disable fedora builds for now. > > Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-2736 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Here a failed build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > The second failure today. > I hope we can fix this quickly. > If not we need to disable fedora builds for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2736) Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
by Nir Soffer (oVirt JIRA) 30 May '19

30 May '19

Nir Soffer created OVIRT-2736: --------------------------------- Summary: Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing Key: OVIRT-2736 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Here a failed build: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… The second failure today. I hope we can fix this quickly. If not we need to disable fedora builds for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[CQ]: 100418,2 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 30 May '19

30 May '19

Change 100418,2 (ovirt-engine) 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/100418/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1028/

1 0

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

30 May '19

A system test invoked by the "ovirt-master" change queue including change 100367,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100312,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100312,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100367/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100312/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14344/

1 0

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

30 May '19

A system test invoked by the "ovirt-master" change queue including change 100313,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100312,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100312,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100313/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100312/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14339/

1 0

[CQ]: 99603, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 30 May '19

30 May '19

Change 99603,1 (ovirt-engine-nodejs-modules) 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/99603/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14334/

1 0

Change in ds-jenkins-stg[master]: Dummy build-art job.
by review＠gerrit-staging.phx.ovirt.org 30 May '19

30 May '19

From Ehud Yonasi <eyonasi(a)redhat.com>: Ehud Yonasi has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/252 ) Change subject: Dummy build-art job. ...................................................................... Dummy build-art job. Change-Id: I861a4ce87f515b4c28668689ab7da2c5ff7f3e66 Signed-off-by: Ehud Yonasi <eyonasi(a)redhat.com> --- A automation/build-artifacts.sh 1 file changed, 2 insertions(+), 0 deletions(-) Approvals: Jenkins CI: Passed CI tests Ehud Yonasi: Looks good to me, approved; Verified -- To view, visit https://gerrit-staging.phx.ovirt.org/252 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: I861a4ce87f515b4c28668689ab7da2c5ff7f3e66 Gerrit-Change-Number: 252 Gerrit-PatchSet: 1 Gerrit-Owner: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ds-jenkins-stg[master]: Dummy build-art job.
by review＠gerrit-staging.phx.ovirt.org 30 May '19

30 May '19

From Ehud Yonasi <eyonasi(a)redhat.com>: Ehud Yonasi has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/252 ) Change subject: Dummy build-art job. ...................................................................... Patch Set 1: Verified+1 Code-Review+2 -- To view, visit https://gerrit-staging.phx.ovirt.org/252 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I861a4ce87f515b4c28668689ab7da2c5ff7f3e66 Gerrit-Change-Number: 252 Gerrit-PatchSet: 1 Gerrit-Owner: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Ehud Yonasi <eyonasi(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Thu, 30 May 2019 10:05:45 +0000 Gerrit-HasComments: No

1 0

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

30 May '19

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

1 0

[CQ]: 100312,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 30 May '19

30 May '19

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

1 0

[CQ]: 100079, 1 (ovirt-engine-api-explorer) failed "ovirt-4.3" system tests
by oVirt Jenkins 30 May '19

30 May '19

Change 100079,1 (ovirt-engine-api-explorer) 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/100079/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1025/

1 0

[CQ]: 99603, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests
by oVirt Jenkins 30 May '19

30 May '19

Change 99603,1 (ovirt-engine-nodejs-modules) 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/99603/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1023/

1 0

Is lfedora1 experiancing some kind of downtime atm?
by Barak Korren 30 May '19

30 May '19

Hi Dan, We're seeing weird errors from jobs we're running on lfedora1, as if some basic binaries like `touch`, and `sleep`, and `git` are missing... Do you know what is going on there? Thanks, Barak. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 5

[JIRA] (OVIRT-2735) Builds on s390x fail again, reason unknown
by Barak Korren (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2735?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2735: ----------------------------------- Assignee: Barak Korren (was: infra) > Builds on s390x fail again, reason unknown > ------------------------------------------ > > Key: OVIRT-2735 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2735 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Barak Korren > > Here are 2 failed builds: > https://jenkins.ovirt.org/job/standard-manual-runner/300/ > https://jenkins.ovirt.org/job/standard-manual-runner/301/ > There are no logs for the failure: > https://jenkins.ovirt.org/job/standard-manual-runner/300//artifact/build-ar… > https://jenkins.ovirt.org/job/standard-manual-runner/300//artifact/build-ar… > This breaks my workflow, running OST before merging patches. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

2 1

[JIRA] (OVIRT-2735) Builds on s390x fail again, reason unknown
by Barak Korren (oVirt JIRA) 30 May '19

30 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2735?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2735: ------------------------------------- the s390x slave is broken again, I'm working on a way where I can just blacklist the s390x builds on the fly when that happens. Here is the patch that is going to do that: https://gerrit.ovirt.org/c/100395 > Builds on s390x fail again, reason unknown > ------------------------------------------ > > Key: OVIRT-2735 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2735 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Here are 2 failed builds: > https://jenkins.ovirt.org/job/standard-manual-runner/300/ > https://jenkins.ovirt.org/job/standard-manual-runner/301/ > There are no logs for the failure: > https://jenkins.ovirt.org/job/standard-manual-runner/300//artifact/build-ar… > https://jenkins.ovirt.org/job/standard-manual-runner/300//artifact/build-ar… > This breaks my workflow, running OST before merging patches. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

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

30 May '19

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

1 0

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

30 May '19

A system test invoked by the "ovirt-master" change queue including change 100370,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 100309,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100309,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100370/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100309/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14315/

1 0

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

30 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/840//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2735) Builds on s390x fail again, reason unknown
by Nir Soffer (oVirt JIRA) 29 May '19

29 May '19

Nir Soffer created OVIRT-2735: --------------------------------- Summary: Builds on s390x fail again, reason unknown Key: OVIRT-2735 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2735 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Here are 2 failed builds: https://jenkins.ovirt.org/job/standard-manual-runner/300/ https://jenkins.ovirt.org/job/standard-manual-runner/301/ There are no logs for the failure: https://jenkins.ovirt.org/job/standard-manual-runner/300//artifact/build-ar… https://jenkins.ovirt.org/job/standard-manual-runner/300//artifact/build-ar… This breaks my workflow, running OST before merging patches. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[CQ]: 100278,1 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 29 May '19

29 May '19

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

1 0

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

29 May '19

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

1 0

[CQ]: e5cfc78 (v2v-conversion-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 29 May '19

29 May '19

Change e5cfc78 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/e5cfc78329c629e6c7a4a46… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1014/

1 0

[JIRA] (OVIRT-2337) Ensure emergency access to PHX production VMs
by Barak Korren (oVirt JIRA) 29 May '19

29 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2337?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2337: ------------------------------------- We only have one access option, if SPICE is not working for some reason - we have no backup. We need to ensure the other options are available as well, at least VNC, and having the console which would probably be way faster then both would be useful as well. > Ensure emergency access to PHX production VMs > --------------------------------------------- > > Key: OVIRT-2337 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2337 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > Make sure that in case of malfunction we have multiple fail-safe ways of gaining access to the PHX production VMs to resolve issues. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

[JIRA] (OVIRT-2337) Ensure emergency access to PHX production VMs
by Evgheni Dereveanchin (oVirt JIRA) 29 May '19

29 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2337?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2337: --------------------------------------------- I don't think this epic is relevant since we have OpenVPN in PHX so SPICE consoles work from any location as long as the OpenVPN machine is running. If I'm misunderstanding we should define what exactly is missing currently and see if it can be implemented securely. > Ensure emergency access to PHX production VMs > --------------------------------------------- > > Key: OVIRT-2337 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2337 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > Make sure that in case of malfunction we have multiple fail-safe ways of gaining access to the PHX production VMs to resolve issues. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100103)

1 0

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

29 May '19

A system test invoked by the "ovirt-4.3" change queue including change 100375,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 99800,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 99800,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100375/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99800/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1011/

1 0

[CQ]: 100079, 1 (ovirt-engine-api-explorer) failed "ovirt-master" system tests
by oVirt Jenkins 29 May '19

29 May '19

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

1 0

[CQ]: 100349, 1 (vdsm-jsonrpc-java) failed "ovirt-master" system tests
by oVirt Jenkins 29 May '19

29 May '19

Change 100349,1 (vdsm-jsonrpc-java) 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/100349/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14298/

1 0

[CQ]: 83846, 2 (ovirt-scheduler-proxy) failed "ovirt-master" system tests
by oVirt Jenkins 29 May '19

29 May '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 592 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 May '19

29 May '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/592/ Build Number: 592 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #592 [Sandro Bonazzola] drop compat-4.1_suite_master [Eyal Edri] drop all kubevirt org jobs from jenkins.ovirt.org [Sandro Bonazzola] mom: add fc30 jobs [Eyal Edri] add mom to v2 projects ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.resize_and_refresh_storage_domain_42 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:1fb4ea93-1bf8-444c-93cf-1e5eac98d183:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: end task:1fb4ea93-1bf8-444c-93cf-1e5eac98d183:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: Running beb0dd4c on lago-compat-4-2-suite-master-engine: lvresize --size +3000M /dev/mapper/vg1_storage-lun0_bdev lago.ssh: DEBUG: Command beb0dd4c on lago-compat-4-2-suite-master-engine returned with 0 lago.ssh: DEBUG: Command beb0dd4c on lago-compat-4-2-suite-master-engine output: Size of logical volume vg1_storage/lun0_bdev changed from 20.00 GiB (5120 extents) to <22.93 GiB (5870 extents). Logical volume vg1_storage/lun0_bdev successfully resized. lago.ssh: DEBUG: start task:ba444d10-5b43-424e-ac4b-bc4c312d8fe4:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: end task:ba444d10-5b43-424e-ac4b-bc4c312d8fe4:Get ssh client for lago-compat-4-2-suite-master-engine: lago.ssh: DEBUG: Running bf0d8632 on lago-compat-4-2-suite-master-engine: cat /root/multipath.txt lago.ssh: DEBUG: Command bf0d8632 on lago-compat-4-2-suite-master-engine returned with 0 lago.ssh: DEBUG: Command bf0d8632 on lago-compat-4-2-suite-master-engine output: 360014052b3dac88632b4d83a1d5014e7 3600140532278b16ac034c57a0a265b56 36001405880b9e5808df488d9b146ac19 36001405d971c82044f04d168ffc9cb5c 36001405e2e761173de54865ad77226ff --------------------- >> 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.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/002_bootstrap.py", line 565, in resize_and_refresh_storage_domain logical_units=luns File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__ self.gen.throw(type, value, traceback) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test_utils/__init__.py", line 264, in TestEvent 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:1fb4ea93-1bf8-444c-93cf-1e5eac98d183:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: end task:1fb4ea93-1bf8-444c-93cf-1e5eac98d183:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: Running beb0dd4c on lago-compat-4-2-suite-master-engine: lvresize --size +3000M /dev/mapper/vg1_storage-lun0_bdev\nlago.ssh: DEBUG: Command beb0dd4c on lago-compat-4-2-suite-master-engine returned with 0\nlago.ssh: DEBUG: Command beb0dd4c on lago-compat-4-2-suite-master-engine output:\n Size of logical volume vg1_storage/lun0_bdev changed from 20.00 GiB (5120 extents) to <22.93 GiB (5870 extents).\n Logical volume vg1_storage/lun0_bdev successfully resized.\n\nlago.ssh: DEBUG: start task:ba444d10-5b43-424e-ac4b-bc4c312d8fe4:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: end task:ba444d10-5b43-424e-ac4b-bc4c312d8fe4:Get ssh client for lago-compat-4-2-suite-master-engine:\nlago.ssh: DEBUG: Running bf0d8632 on lago-compat-4-2-suite-master-engine: cat /root/multipath.txt\nlago.ssh: DEBUG: Command bf0d8632 on lago-compat-4-2-suite-master-engine returned with 0\nlago.ssh: DEBUG: Command bf0d8632 on lago-compat-4-2-suite-master-engine output:\n 360014052b3dac88632b4d83a1d5014e7\n3600140532278b16ac034c57a0a265b56\n36001405880b9e5808df488d9b146ac19\n36001405d971c82044f04d168ffc9cb5c\n36001405e2e761173de54865ad77226ff\n\n--------------------- >> end captured logging << ---------------------'

1 1

[CQ]: 99378,10 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 29 May '19

29 May '19

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

1 0

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

29 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/839//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 100335,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 100335,1 (vdsm) 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/100335/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1007/

1 0

[CQ]: 99842,2 (ovirt-engine-nodejs) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 99842,2 (ovirt-engine-nodejs) 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/99842/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1005/

1 0

[CQ]: 100079, 1 (ovirt-engine-api-explorer) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 May '19

28 May '19

Change 100079,1 (ovirt-engine-api-explorer) 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/100079/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1002/

1 0