- Infra - oVirt List Archives

[CQ]: 279, 6 (stage-stdci2) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Aug '19

06 Aug '19

A system test invoked by the "dummy-master" change queue including change 279,6 (stage-stdci2) failed. However, this change seems not to be the root cause for this failure. Change 310,1 (stage-stdci2) 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 310,1 (stage-stdci2) 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-staging.phx.ovirt.org/#/c/279/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit-staging.phx.ovirt.org/#/c/310/1 For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/226/

1 0

[CQ]: 369,1 (dummy-system-tests) failed "dummy-master" system tests
by oVirt Jenkins 06 Aug '19

06 Aug '19

Change 369,1 (dummy-system-tests) is probably the reason behind recent system test failures in the "dummy-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-staging.phx.ovirt.org/#/c/369/1 For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/224/

1 0

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

05 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/153/ Build Number: 153 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #153 [Galit Rosenthal] Update missing packages ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.disk_operations_43 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.utils: DEBUG: Error while running thread Thread-84 Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) 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 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *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 514, in live_storage_migration lambda: api.follow_link(disk_service.get().storage_domains[0]).name == SD_ISCSI_NAME 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 --------------------- >> end captured logging << --------------------- Stack Trace: 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 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *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 932, in disk_operations vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) 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 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *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 514, in live_storage_migration lambda: api.follow_link(disk_service.get().storage_domains[0]).name == SD_ISCSI_NAME 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) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nlago.utils: DEBUG: Error while running thread Thread-84\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': func()})\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper\n return func(get_test_prefix(), *args, **kwargs)\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper\n prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs\n 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 514, in live_storage_migration\n lambda: api.follow_link(disk_service.get().storage_domains[0]).name == SD_ISCSI_NAME\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long\n assert_equals_within_long(func, True, allowed_exceptions)\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long\n func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within\n \'%s != %s after %s seconds\' % (res, value, timeout)\nAssertionError: False != True after 600 seconds\n--------------------- >> end captured logging << ---------------------'

1 1

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

05 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/908//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 102274, 4 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Aug '19

05 Aug '19

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

1 0

[CQ]: 102273,4 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 05 Aug '19

05 Aug '19

Change 102273,4 (ovirt-engine) 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://gerrit.ovirt.org/#/c/102273/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1768/

1 0

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

05 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*: RED (#1) Last failure was on 01-08 for ovirt-ansible-hosted-engine-setup caused by missing dependency, patch is pending to fix this. *CQ-4.3*: RED (#1) Last failure was on 02-08 for vdsm caused by missing dependency, patch is pending to fix this. *CQ-Master:* RED (#1) Last failure was on 02-08 for ovirt-engine due failure in build-artifacts, which was caused by gerrit issue, which was reported Evgheni. 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-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… 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/YCNCKRK3G4EJX…

5 5

[JIRA] (OVIRT-2770) developer in github.com/oVirt
by Eyal Edri (oVirt JIRA) 05 Aug '19

05 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2770?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2770: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > developer in github.com/oVirt > ----------------------------- > > Key: OVIRT-2770 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2770 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eitan Raviv > Assignee: infra > > Hi, > Could you pls add me as developer to oVirt? > My github id: github.com/erav/ > Thanks -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100107)

1 0

[oVirt CI] standard-enqueue - Build #23124 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Aug '19

05 Aug '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/23124/ Build Name: #23124 Build Description: Gerrit: 102364 - ovirt-engine (4.3.5.z) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/102364 - title: packaging: setup: Fix incompatible snapshots test - project: ovirt-engine - branch: ovirt-engine-4.3.5.z - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 2

[CQ]: 102372, 4 (ovirt-host-deploy) failed "ovirt-master" system tests
by oVirt Jenkins 05 Aug '19

05 Aug '19

Change 102372,4 (ovirt-host-deploy) 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/102372/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15269/

1 0