- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 953 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Oct '18

22 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build Number: 953 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #953 [Yuval Turgeman] automation: remove build-artifacts* from stdci-v2 ----------------- Failed Tests: ----------------- No tests ran.

1 4

[CQ]: f86dbef (ovirt-ansible-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 22 Oct '18

22 Oct '18

Change f86dbef (ovirt-ansible-engine-setup) 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://github.com/oVirt/ovirt-ansible-engine-setup/commit/f86dbef406d2c0b1… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10888/

1 0

[JIRA] (OVIRT-2553) add memory to resources
by Evgheni Dereveanchin (oVirt JIRA) 22 Oct '18

22 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2553?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2553: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > add memory to resources > ----------------------- > > Key: OVIRT-2553 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2553 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > After adding memory monitoring to resources it's obvious that this system can use more RAM. While OVIRT-2477 is the main ticket, a short-term solution is just to double the RAM from 2GB to 4GB. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2553) add memory to resources
by Evgheni Dereveanchin (oVirt JIRA) 22 Oct '18

22 Oct '18

Evgheni Dereveanchin created OVIRT-2553: ------------------------------------------- Summary: add memory to resources Key: OVIRT-2553 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2553 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra After adding memory monitoring to resources it's obvious that this system can use more RAM. While OVIRT-2477 is the main ticket, a short-term solution is just to double the RAM from 2GB to 4GB. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

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

22 Oct '18

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

1 0

[CQ]: 95049, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Oct '18

22 Oct '18

Change 95049,1 (ovirt-hosted-engine-setup) 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/95049/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3387/

3 2

[CQ]: 94732, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 Oct '18

22 Oct '18

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 22 Oct '18

22 Oct '18

Failed to run project_setup.sh for: #2049 ovirt-system-tests [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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Oct '18

22 Oct '18

Failed to run project_setup.sh for: #2334 kubevirt [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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Oct '18

22 Oct '18

Failed to run project_setup.sh for: #2334 kubevirt [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 ovirt-srv04.phx.ovirt.org-container-1.

1 0