March 2021 - Infra - Ovirt List Archives

[CQ]: 113999, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 113999,2 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 113144,5 (ovirt-system-tests) 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 113144,5 (ovirt-system-tests) 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-system-tests/+/#/c/113999/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-system-tests/+/#/c/113144/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/28784/

3 years, 7 months

1
0
0 / 0

[CQ]: 113822, 4 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

3 years, 7 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 313 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nigh... Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nigh... Build Number: 313 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #313 [Martin Perina] network: Readd network-suite-4.3 from check-patch ----------------- Failed Tests: ----------------- No tests ran.

3 years, 7 months

1
2
0 / 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 984 - Failure!

by jenkins＠jenkins.phx.ovirt.org

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_night... Build Number: 984 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #984 [Yedidyah Bar David] Do not have a config_builder inside ModuleMapper ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.test_007_sd_reattach.test_deactivate_storage_domain Error Message: ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot deactivate Storage. Storage Domain OVF data is currently being updated.]". HTTP response code is 409. Stack Trace: engine_api = <ovirtsdk4.Connection object at 0x7f68901929e8> @order_by(_TEST_LIST) def test_deactivate_storage_domain(engine_api): # TODO: uncomment once VnicSetup checks are fixed. # TODO: this also seems to leave running tasks behind which break the deactivation. # TODO: it should be tested in multiple runs or properly waited for. # VnicSetup.vnic_setup().init(engine_api.system_service(), # VM2_NAME, DC_NAME, CLUSTER_NAME) dc = test_utils.data_center_service(engine_api.system_service(), DC_NAME) test_utils.get_attached_storage_domain( > dc, SD_SECOND_NFS_NAME, service=True).deactivate() basic-suite-master/test-scenarios/test_007_sd_reattach.py:63: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python3.6/site-packages/ovirtsdk4/services.py:3392: in deactivate return self._internal_action(action, 'deactivate', None, headers, query, wait) /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:299: in _internal_action return future.wait() if wait else future /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:55: in wait return self._code(response) /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:296: in callback self._check_fault(response) /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:134: in _check_fault self._raise_error(response, body.fault) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ response = <ovirtsdk4.http.Response object at 0x7f6890192f60> detail = <ovirtsdk4.types.Fault object at 0x7f6890192390> @staticmethod def _raise_error(response, detail=None): """ Creates and raises an error containing the details of the given HTTP response and fault. This method is intended for internal use by other components of the SDK. Refrain from using it directly, as backwards compatibility isn't guaranteed. """ fault = detail if isinstance(detail, types.Fault) else None msg = '' if fault: if fault.reason: if msg: msg += ' ' msg = msg + 'Fault reason is "%s".' % fault.reason if fault.detail: if msg: msg += ' ' msg = msg + 'Fault detail is "%s".' % fault.detail if response: if response.code: if msg: msg += ' ' msg = msg + 'HTTP response code is %s.' % response.code if response.message: if msg: msg += ' ' msg = msg + 'HTTP response message is "%s".' % response.message if isinstance(detail, six.string_types): if msg: msg += ' ' msg = msg + detail + '.' class_ = Error if response is not None: if response.code in [401, 403]: class_ = AuthError elif response.code == 404: class_ = NotFoundError error = class_(msg) error.code = response.code if response else None error.fault = fault > raise error E ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot deactivate Storage. Storage Domain OVF data is currently being updated.]". HTTP response code is 409. /usr/lib64/python3.6/site-packages/ovirtsdk4/service.py:118: Error

3 years, 8 months

1
1
0 / 0

oVirt infra daily report - unstable production jobs - 1504

by jenkins＠jenkins.phx.ovirt.org

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/1504//artifact/export... Cheers, Jenkins

3 years, 8 months

1
0
0 / 0

[CQ]: 113450, 13 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

3 years, 8 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 317 - Failure!

by jenkins＠jenkins.phx.ovirt.org

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/... Build Number: 317 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #317 [Martin Perina] network: Readd network-suite-4.3 from check-patch ----------------- 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.

3 years, 8 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_el7-nightly - Build # 310 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nigh... Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_el7-nigh... Build Number: 310 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #310 [Martin Perina] network: Readd network-suite-4.3 from check-patch ----------------- Failed Tests: ----------------- No tests ran.

3 years, 8 months

1
2
0 / 0

oVirt infra daily report - unstable production jobs - 1503

by jenkins＠jenkins.phx.ovirt.org

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/1503//artifact/export... Cheers, Jenkins

3 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-3090) Image Request - openSUSE Kubic & Arch Linux Cloud Image

by Okami Dash (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3090?page=com.atlassian.jir... ] Okami Dash updated OVIRT-3090: ------------------------------ Priority: Low (was: Medium) > Image Request - openSUSE Kubic & Arch Linux Cloud Image > ------------------------------------------------------- > > Key: OVIRT-3090 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3090 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt image repository (Glance) > Reporter: Okami Dash > Assignee: infra > Priority: Low > > Hi, > I'd like to request, if possible; that the following Openstack-compatible images are made available on your Openstack Glance image provider. > - [openSUSE kubic|https://en.opensuse.org/Portal:Kubic/Downloads] > - [Arch Linux|https://gitlab.archlinux.org/archlinux/arch-boxes/-/jobs/artifacts/...] > Each are linked to where you can download the images. > They are both provided officially and offer cloud-init compatability. > I am more than happy to provide maintenance and whatever support is needed to get these both integrated. > If you would like me to run integration tests, I am also more than happy to run it on my dev instance of oVirt. If requested, I can also see what I can do to provide a 'machine configuration', i.e Virtio, sata, etc for each VM. > In addition to the above distros, while I do not use them; they would be useful for other members to have integrated (and I am also happy to do the testing required for these). Public cloud images are also available. > - openSUSE Leap > - openSUSE Tumbleweed > - openSUSE MicroOS > - flatcar Linux -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100156)

3 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra March 2021