- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 718 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Aug '21

04 Aug '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/71… Build Number: 718 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #718 [parthdhanjal] Updating max click version ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms Error Message: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400. 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 "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/004_basic_sanity.py", line 694, in run_vms vm0_service.start(use_cloud_init=True, vm=vm_params) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 32520, in start return self._internal_action(action, 'start', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Error: Fault reason is "Operation Failed". Fault detail is "[Network error during communication with the Host.]". HTTP response code is 400.

1 2

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1380 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Aug '21

04 Aug '21

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1380 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1380 [Andrej Cernek] black: Apply black to selenium ost_utils ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_004_basic_sanity.test_live_incremental_backup_vm2 Error Message: AssertionError: False != True after 600 seconds Stack Trace: engine_api = <ovirtsdk4.Connection object at 0x7f30b47c33c8> get_vm_service_for_vm = <function get_vm_service_for_vm.<locals>.service_for at 0x7f30b25f5488> @order_by(_TEST_LIST) def test_live_incremental_backup_vm2(engine_api, get_vm_service_for_vm): _verify_vm_state(engine_api.system_service(), VM2_NAME, types.VmStatus.UP) vm2_backups_service = get_vm_service_for_vm(VM2_NAME).backups_service() backup.perform_incremental_vm_backup( > engine_api, vm2_backups_service, DISK2_NAME, "live_vm_backup") basic-suite-master/test-scenarios/test_004_basic_sanity.py:1089: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ost_utils/ost_utils/storage_utils/backup.py:81: in perform_incremental_vm_backup correlation_id="full_" + correlation_id, ost_utils/ost_utils/storage_utils/backup.py:50: in perform_vm_backup allowed_exceptions=[sdk4.NotFoundError], ost_utils/ost_utils/assertions.py:96: in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) ost_utils/ost_utils/assertions.py:81: in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ func = <function perform_vm_backup.<locals>.<lambda> at 0x7f30b2482ae8> value = True, timeout = 600 allowed_exceptions = [<class 'ovirtsdk4.NotFoundError'>], initial_wait = 0 error_message = 'False != True after 600 seconds' def assert_equals_within( func, value, timeout, allowed_exceptions=None, initial_wait=10, error_message=None ): allowed_exceptions = allowed_exceptions or [] res = '<no-result-obtained>' with _EggTimer(timeout) as timer: while not timer.elapsed(): try: res = func() if res == value: return except Exception as exc: if _instance_of_any(exc, allowed_exceptions): time.sleep(3) continue LOGGER.exception("Unhandled exception in %s", func) raise if initial_wait == 0: time.sleep(3) else: time.sleep(initial_wait) initial_wait = 0 try: if error_message is None: error_message = '%s != %s after %s seconds' % (res, value, timeout) > raise AssertionError(error_message) E AssertionError: False != True after 600 seconds ost_utils/ost_utils/assertions.py:59: AssertionError

1 1

[CQ]: 116021, 2 (ovirt-node-ng-image) failed "ovirt-4.4" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Aug '21

04 Aug '21

A system test invoked by the "ovirt-4.4" change queue including change 116021,2 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 116009,1 (ovirt-node-ng-image) 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 116009,1 (ovirt-node-ng-image) 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/ovirt-node-ng-image/+/#/c/116021/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-node-ng-image/+/#/c/116009/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.4_change-queue-tester/434/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #689 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 04 Aug '21

04 Aug '21

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

1 10

[CQ]: 116020, 2 (ovirt-node-ng-image) failed "ovirt-4.4" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Aug '21

04 Aug '21

A system test invoked by the "ovirt-4.4" change queue including change 116020,2 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 116009,1 (ovirt-node-ng-image) 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 116009,1 (ovirt-node-ng-image) 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/ovirt-node-ng-image/+/#/c/116020/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/c/ovirt-node-ng-image/+/#/c/116009/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.4_change-queue-tester/433/

1 0

oVirt infra daily report - unstable production jobs - 1637
by jenkins＠jenkins.phx.ovirt.org 04 Aug '21

04 Aug '21

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1637//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 116022, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Aug '21

03 Aug '21

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

1 0

[CQ]: 116019, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Aug '21

03 Aug '21

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

1 0

[CQ]: 116031, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Aug '21

03 Aug '21

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

1 0

[CQ]: 116018, 1 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Aug '21

03 Aug '21

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

1 0