- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 723
by jenkins＠jenkins.phx.ovirt.org 01 Feb '19

01 Feb '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/723//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97491, 3 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 01 Feb '19

01 Feb '19

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

1 0

[Ovirt] [CQ weekly status] [01-02-2019]
by Dafna Ron 01 Feb '19

01 Feb '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#2) We have no current failures. Last failed job was for ovirt-ansible-hosted-engine-setup due to build-artiacts job on Jan 25. the issue is worked on by Simon Tiraboschi *CQ-Master:* GREEN (#1) There are no current issues in master CQ During the week we had 3 regressions for ovirt-engine 1. Domain version 5 feature was merged but its was not yet supported on vdsm side: https://gerrit.ovirt.org/#/c/96178/ - storage: Added V5 domain format definition. Date failure in CQ: 24-01-2019 test failing: 002_bootstrap.add_master_storage_domain Fix: https://gerrit.ovirt.org/#/c/97262/ - storage: Make default domain verion V4 for 4.3 2. CQ was still failing on create domain v5 after the fix was merged to fix regression #1 https://gerrit.ovirt.org/#/c/96178/ - storage: Added V5 domain format definition. Date failure in CQ: 26-01-2019 test failing: 002_bootstrap.add_secondary_storage_domains Fix: https://gerrit.ovirt.org/#/c/97408/ - storage: V5 is not a latest domain version yet ** first patch fixed the domain create for manual create but via the API the version was available which is why we were still failing on CQ. 3. Added callbacks for MBS disks causing regular disks to use callbacks unnecessarily https://gerrit.ovirt.org/#/c/96815/ - core: set VmDevices properly when creating and attaching We saw this regression once #1 and #2 regressions were fixed. Date first failure detected: 30-01-2019 Fix: https://gerrit.ovirt.org/#/c/97428/ - core: partial revert of 4d439006 Ovirt-engine passed on 31-01-2019 Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

[CQ]: 97397,7 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 31 Jan '19

31 Jan '19

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

1 0

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

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

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

Failed to run project_setup.sh for: #3402 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 openshift-kubevirt-org-77p5l.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

Failed to run project_setup.sh for: #3401 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 openshift-kubevirt-org-2f4nn.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

Failed to run project_setup.sh for: #3398 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 openshift-kubevirt-org-chplw.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 31 Jan '19

31 Jan '19

Failed to run project_setup.sh for: #3398 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 openshift-kubevirt-org-trzjs.

1 0

[CQ]: 97452,5 (py2exe-py2.7) failed "ovirt-master" system tests
by oVirt Jenkins 31 Jan '19

31 Jan '19

Change 97452,5 (py2exe-py2.7) 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/97452/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12616/

1 0