- Infra - oVirt List Archives

[CQ]: 116073, 10 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Aug '21

23 Aug '21

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

1 0

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

23 Aug '21

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

1 1

[CQ]: 116220, 2 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Aug '21

23 Aug '21

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

1 0

[oVirt Jenkins] cleanup-gated-ovirt-master - Build #608 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Aug '21

23 Aug '21

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

1 4

[JIRA] (OVIRT-3116) Fail fast on unsupported configuration
by Evgheni Dereveanchin (oVirt JIRA) 23 Aug '21

23 Aug '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3116?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-3116: --------------------------------------------- [~accountid:5aa0f39f5a4d022884128a0f] could you please check how this can be implemented? I had a feeling that failing jobs if the distro is unknown was expected behavior. > Fail fast on unsupported configuration > -------------------------------------- > > Key: OVIRT-3116 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3116 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > When using: > host-distro: el8 > The CI ignores the unknown configuration "el8" runs the job anywhere. > Then the job fails after many minutes, wasting resources and developers > time running on el7, where the tests cannot pass. > Lets fix to fail fast on the first unknown configuration, don't run anything > if the configuration is invalid. > Example builds: > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29292/ > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29293/ > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/29295/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100174)

1 0

[CQ]: 116212, 3 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Aug '21

23 Aug '21

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

1 0

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

23 Aug '21

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

1 0

[oVirt Jenkins] ovirt-release_master_build-artifacts-el7-x86_64 - Build # 1955 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Aug '21

23 Aug '21

Project: https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_… Build: https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_… Build Number: 1955 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1955 [Sandro Bonazzola] el9s: add x86_64 initial repos ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

23 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/1656//artifact/exported… Cheers, Jenkins

1 0

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

22 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/77… Build Number: 772 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #772 [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 1