- Infra - oVirt List Archives

[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 29 May '19

29 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 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/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