- Infra - oVirt List Archives

[ovirt-devel] [Ovirt] [CQ weekly status] [10-08-2019]
by Dusan Fodor 11 Aug '19

11 Aug '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 (#3) No failure during this week. *CQ-4.3*: RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] *CQ-Master:* RED (#1) Last failure was on 10-08 for ovirt-ansible-image-template in verify_glance_import. This issue is ongoing, investigation will continue under thread [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.2_change-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- 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) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt .org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

2 1

[CQ]: 101095, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Aug '19

11 Aug '19

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

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #1 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Aug '19

11 Aug '19

Build: http://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/1/ Build Name: #1 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 2

[CQ]: 88eb306 (ovirt-ansible-disaster-recovery) failed "ovirt-4.3" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

Change 88eb306 (ovirt-ansible-disaster-recovery) 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/ovirt-ansible-disaster-recovery/commit/88eb3068759… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1810/

1 0

[CQ]: 88eb306 (ovirt-ansible-disaster-recovery) failed "ovirt-4.2" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

Change 88eb306 (ovirt-ansible-disaster-recovery) 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://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/88eb3068759… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4700/

1 0

[CQ]: 88eb306 (ovirt-ansible-disaster-recovery) failed "ovirt-master" system tests
by oVirt Jenkins 11 Aug '19

11 Aug '19

Change 88eb306 (ovirt-ansible-disaster-recovery) 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-disaster-recovery/commit/88eb3068759… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15354/

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 157 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Aug '19

11 Aug '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/157/ Build Number: 157 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #157 [Galit Rosenthal] Remove ansible exclude ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.verify_glance_import_43 Error Message: False != True after 600 seconds Stack Trace: Traceback (most recent call last): 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 69, in wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/004_basic_sanity.py", line 1130, in verify_glance_import lambda: api.disks.get(disk_name).status.state == 'ok', 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) AssertionError: False != True after 600 seconds

1 2

oVirt infra daily report - unstable production jobs - 913
by jenkins＠jenkins.phx.ovirt.org 11 Aug '19

11 Aug '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/913//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2773) verify_glance_import test failing in both 4.3 and master suites
by Dusan Fodor (oVirt JIRA) 10 Aug '19

10 Aug '19

Dusan Fodor created OVIRT-2773: ---------------------------------- Summary: verify_glance_import test failing in both 4.3 and master suites Key: OVIRT-2773 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2773 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dusan Fodor Assignee: infra Example of failed job can be found here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… Thread [ovirt-devel] [OST Failure Report] [oVirt master&4.3] [09-08-2019] [verify_glance_import] was opened for investigation -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[CQ]: 5191b28 (ovirt-ansible-image-template) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Aug '19

10 Aug '19

A system test invoked by the "ovirt-master" change queue including change 5191b28 (ovirt-ansible-image-template) failed. However, this change seems not to be the root cause for this failure. Change e5d0b24 (ovirt-ansible-image- template) 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 e5d0b24 (ovirt-ansible-image- template) 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://github.com/oVirt/ovirt-ansible-image-template/commit/5191b28583c183… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-image-template/commit/e5d0b2427fd0b8… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15352/

1 0