- Infra - oVirt List Archives

[CQ]: 92025, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Jun '18

08 Jun '18

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

1 0

[CQ]: 92077, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Jun '18

08 Jun '18

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

1 0

[CQ]: 87727, 1 (ovirt-engine-api-explorer) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Jun '18

07 Jun '18

Change 87727,1 (ovirt-engine-api-explorer) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/87727/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2337/

1 0

[CQ]: 92077, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Jun '18

07 Jun '18

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

1 0

[CQ]: 90889, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.1" system tests
by oVirt Jenkins 07 Jun '18

07 Jun '18

Change 90889,1 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/90889/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1809/

1 0

[CQ]: 90889, 1 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Jun '18

07 Jun '18

Change 90889,1 (ovirt-engine-nodejs-modules) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/90889/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2333/

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by sbonazzo (oVirt JIRA) 07 Jun '18

07 Jun '18

sbonazzo created OVIRT-2153: ------------------------------- Summary: Fedora 28 ppc64le support Key: OVIRT-2153 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable to find mock env" error. I tend to think we should have ppc64le for fedora 28 but I see that mock config are missing in jenkins and also the mirroring of the repos for fedora 28 ppc64le are missing. We should either drop ppc64le jobs for fc28 or add support for it. Adding Ondra to share his thoughts on this. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 91538,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 07 Jun '18

07 Jun '18

Change 91538,4 (ovirt-engine-sdk) 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/91538/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8092/

1 0

what is the current best way for a UX designer to verify a patch?
by Greg Sheremeta 07 Jun '18

07 Jun '18

Hey, I'm unsure of the state of OST / Orb as far as a demo tool. I want a single push button operation so Liz can verify UI patches. Can we do that? Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

2 2

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 239 - Failure!
by jenkins＠jenkins.phx.ovirt.org 07 Jun '18

07 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/239/ Build Number: 239 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #239 [Gal Ben Haim] Remove 4.1 suites automation files [Daniel Belenky] DSL: Do not normalize release_branches values ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Host lago-hc-basic-suite-4-2-host1 is in non responsive state -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fb07c5400c8> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 263, in _host_is_up_4 raise RuntimeError('Host %s is in non responsive state' % api_host.name) RuntimeError: Host lago-hc-basic-suite-4-2-host1 is in non responsive state --------------------- >> 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 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 263, in _host_is_up_4 raise RuntimeError('Host %s is in non responsive state' % api_host.name) 'Host lago-hc-basic-suite-4-2-host1 is in non responsive state\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fb07c5400c8>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 263, in _host_is_up_4\n raise RuntimeError(\'Host %s is in non responsive state\' % api_host.name)\nRuntimeError: Host lago-hc-basic-suite-4-2-host1 is in non responsive state\n--------------------- >> end captured logging << ---------------------'

1 1