- Infra - oVirt List Archives

[CQ]: 112728, 15 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Feb '21

03 Feb '21

A system test invoked by the "ovirt-master" change queue including change 112728,15 (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/112728/15 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/27975/

1 0

[CQ]: 112727, 12 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Feb '21

03 Feb '21

A system test invoked by the "ovirt-master" change queue including change 112727,12 (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/112727/12 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/27973/

1 0

[CQ]: 112726, 12 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Feb '21

03 Feb '21

A system test invoked by the "ovirt-master" change queue including change 112726,12 (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/112726/12 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/27972/

1 0

[CQ]: 112725, 8 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Feb '21

03 Feb '21

A system test invoked by the "ovirt-master" change queue including change 112725,8 (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/112725/8 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/27971/

1 0

[JIRA] (OVIRT-3085) ovirt-system-tests_manual job config
by Vojtech Juranek (oVirt JIRA) 03 Feb '21

03 Feb '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3085?page=com.atlassian.jira.… ] Vojtech Juranek commented on OVIRT-3085: ---------------------------------------- Ack, thanks > ovirt-system-tests_manual job config > ------------------------------------ > > Key: OVIRT-3085 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3085 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST Manual job > Reporter: Vojtech Juranek > Assignee: infra > > To run ovirt-system-tests_manual job with custom repo, one needs > to provide full path to the repo, e.g. > https://jenkins.ovirt.org/job/standard-manual-runner/1680/artifact/build-ar… > Until recently, it was sufficient to provide just link to the job which > built the repo, e.g. > https://jenkins.ovirt.org/job/standard-manual-runner/1680/ > Would it be possible to move back to old config so that only job link > is sufficient? This change breaks our automation, ovirt-ci tool doesn't > work with it, see > https://github.com/nirs/ovirt-ci/issues/50 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154)

1 0

[JIRA] (OVIRT-3085) ovirt-system-tests_manual job config
by Marcin Sobczyk (oVirt JIRA) 03 Feb '21

03 Feb '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3085?page=com.atlassian.jira.… ] Marcin Sobczyk edited comment on OVIRT-3085 at 2/3/21 10:32 AM: ---------------------------------------------------------------- [~accountid:557058:42767862-fc29-47f5-aaab-17e88f11d751] it’s a bit complicated, but doable I think. I [filed a task for this|https://issues.redhat.com/browse/RHV-40941] Please see the description on why this happens. Since we have a separate board for non-CI OST tasks I’d close this one. was (Author: msobczyk): [~accountid:557058:42767862-fc29-47f5-aaab-17e88f11d751] it’s a bit complicated, but doable I think. I [filed a task for this|https://issues.redhat.com/browse/RHV-40941] Please see the description on why this happens. > ovirt-system-tests_manual job config > ------------------------------------ > > Key: OVIRT-3085 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3085 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST Manual job > Reporter: Vojtech Juranek > Assignee: infra > > To run ovirt-system-tests_manual job with custom repo, one needs > to provide full path to the repo, e.g. > https://jenkins.ovirt.org/job/standard-manual-runner/1680/artifact/build-ar… > Until recently, it was sufficient to provide just link to the job which > built the repo, e.g. > https://jenkins.ovirt.org/job/standard-manual-runner/1680/ > Would it be possible to move back to old config so that only job link > is sufficient? This change breaks our automation, ovirt-ci tool doesn't > work with it, see > https://github.com/nirs/ovirt-ci/issues/50 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154)

1 0

[JIRA] (OVIRT-3085) ovirt-system-tests_manual job config
by Marcin Sobczyk (oVirt JIRA) 03 Feb '21

03 Feb '21

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3085?page=com.atlassian.jira.… ] Marcin Sobczyk commented on OVIRT-3085: --------------------------------------- [~accountid:557058:42767862-fc29-47f5-aaab-17e88f11d751] it’s a bit complicated, but doable I think. I [filed a task for this|https://issues.redhat.com/browse/RHV-40941] Please see the description on why this happens. > ovirt-system-tests_manual job config > ------------------------------------ > > Key: OVIRT-3085 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3085 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST Manual job > Reporter: Vojtech Juranek > Assignee: infra > > To run ovirt-system-tests_manual job with custom repo, one needs > to provide full path to the repo, e.g. > https://jenkins.ovirt.org/job/standard-manual-runner/1680/artifact/build-ar… > Until recently, it was sufficient to provide just link to the job which > built the repo, e.g. > https://jenkins.ovirt.org/job/standard-manual-runner/1680/ > Would it be possible to move back to old config so that only job link > is sufficient? This change breaks our automation, ovirt-ci tool doesn't > work with it, see > https://github.com/nirs/ovirt-ci/issues/50 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154)

1 0

Please provide me access to Jenkins staging
by Galit Rosenthal 03 Feb '21

03 Feb '21

Thanks -- Galit Rosenthal SOFTWARE ENGINEER Red Hat <https://www.redhat.com/> galit(a)redhat.com T: 972-9-7692230 <https://www.redhat.com/>

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 172 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Feb '21

03 Feb '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/17… Build Number: 172 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #172 [parthdhanjal] WIP: hc-4.3 fix ----------------- 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

oVirt infra daily report - unstable production jobs - 1455
by jenkins＠jenkins.phx.ovirt.org 03 Feb '21

03 Feb '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/1455//artifact/exported… Cheers, Jenkins

1 0