June 2018 - Infra - oVirt List Archives

[CQ]: 92319, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jun '18

28 Jun '18

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

1 0

[CQ]: 92318, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jun '18

28 Jun '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 283 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '18

28 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 283 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #283 [Gal Ben Haim] Make sure that crond is installed and running [Barak Korren] Install JJB via PIP instead of YUM [Barak Korren] Clean deprecation warning from JJB output [Barak Korren] Upgrade JJB to 1.6.2 ----------------- Failed Tests: ----------------- All tests passed

1 1

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

28 Jun '18

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

1 0

[CQ]: 92149, 13 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jun '18

28 Jun '18

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

1 0

[JIRA] (OVIRT-2263) add uxd to oVirt github developers group
by Greg Sheremeta (oVirt JIRA) 27 Jun '18

27 Jun '18

Greg Sheremeta created OVIRT-2263: ------------------------------------- Summary: add uxd to oVirt github developers group Key: OVIRT-2263 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2263 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hi, How can I add people to the oVirt github developers group? https://github.com/orgs/oVirt/teams/developers need to add our designers: https://github.com/lizsurette https://github.com/jennyhaines Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 92567,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 27 Jun '18

27 Jun '18

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

1 0

[CQ]: 92313,2 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 27 Jun '18

27 Jun '18

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

1 0

[JIRA] (OVIRT-2255) build aborted on time out
by Gal Ben Haim (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2255?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2255: ------------------------------------- # attach_vm_network_to_host_0_static_config: Success (in 1:08:46) The test above took ~1 hour, [~lgoldber] [~ehaas(a)redhat.com] can you please take a look? > build aborted on time out > -------------------------- > > Key: OVIRT-2255 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2255 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_lago > > We had a test aborted which seemed to have been on time out. > Build was aborted: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8350/ > I can see it was a timeout: Timeout has been exceeded > sigterm was sent by lago: > '+ logger.success 'Cleanup done' > + logger.log SUCCESS 'Cleanup done' > + set +x > run_suite.sh::env_cleanup::SUCCESS:: Cleanup done > + exit 0 > + exit > Sending interrupt signal to process > sh: line 1: 47038 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/script.sh' > '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/jenkins-log.txt' 2>&1 > After 10s process did not stop' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Gal Ben Haim (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2231: -------------------------------- Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) > QEMU can't access "/home/jenkins/*" on FC28 slaves. > --------------------------------------------------- > > Key: OVIRT-2231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2231 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > Priority: Highest > > Lago creates VM images under "/home/jenkins", QEMU process fails to access those images because of missing permissions. > The solution is to set the "execute/search" bit on "/home/jenkins". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0