December 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2620) Mirroring error
by Eyal Edri (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2620?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2620: ---------------------------------- [~bkorren(a)redhat.com] any idea? > Mirroring error > --------------- > > Key: OVIRT-2620 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2620 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > *Hi,* > *looks like in our mirror script there's a bug, we don't clean the > <repo>/gen directory before starting the mirroring* > *04:35:12* yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/centos-kvm-common-el7/gen error was: > [Errno 17] File exists: > '/home/jenkins/mirrors_cache/centos-kvm-common-el7/gen' > Job: > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > 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#100095)

1 0

[CQ]: 96078,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Dec '18

12 Dec '18

Change 96078,5 (vdsm) 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/96078/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11968/

2 1

[JIRA] (OVIRT-2619) Jenkins network extremely slow
by Barak Korren (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2619?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2619: ------------------------------------- This is using the proxy: {code} 00:01:44.031 Using proxified config /home/jenkins/workspace/ovirt-appliance_ovirt-4.3_build-artifacts-fc28-x86_64/jenkins/mock_configs/fedora-28-x86_64_proxied.cfg {code} [~ederevea] can we check if the proxy became slow or unresponsive? > Jenkins network extremely slow > ------------------------------ > > Key: OVIRT-2619 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2619 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Jenkins Slaves > Reporter: sbonazzo > Assignee: infra > Priority: High > Labels: network > > Looking at: > https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x… > Download of Fedora Boot ISO: > *08:10:57* curl -L -O > "http://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_6…"*08:10:57* > % Total % Received % Xferd Average Speed Time Time Time > Current*08:10:57* Dload Upload > Total Spent Left Speed > It took ~ 2 hours to get the download running and then: > 83 583M 83 484M 0 0 82299 0 2:03:48 1:42:55 > 0:20:53 33902*09:53:57* curl: (92) HTTP/2 stream 1 was not closed > cleanly: INTERNAL_ERROR (err 2) > Can you please check connectivity? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > 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#100095)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Failed to run project_setup.sh for: #2890 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-6lj84.

1 0

[JIRA] (OVIRT-2621) setlocale warnings in mock logs
by Barak Korren (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2621?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2621: ------------------------------------- I think this is specific to the node-ng build job that was linked to. It seems to be trying to run the 'setlocale' command on multiple occasions and failing. It looks like it can be a simple matter of installing the right package in the {{*. packages}} file. Looking at my own RHEL workstation - I don't have the 'setlocale' command - so it may have been deprecated or move around at some point. > setlocale warnings in mock logs > ------------------------------- > > Key: OVIRT-2621 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2621 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > There's a bunch of setlocale warnings in mock logs which didn't exist before: > https://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-e… > We need to verify what happened to get rid of these messages as they are distracting attention from real failure causes -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 386 - Failure!
by jenkins＠jenkins.phx.ovirt.org 12 Dec '18

12 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/386/ Build Number: 386 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #386 [Dan Kenigsberg] basic suite: use fancy bond names ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 003_basic_networking.bond_nics_41 Error Message: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6d9320> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', 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 132, in _check_fault self._raise_error(response, body) 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 "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', 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 132, in _check_fault self._raise_error(response, body) 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 "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. ovirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6a47d0> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', 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 132, in _check_fault self._raise_error(response, body) 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 "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. lago.utils: ERROR: Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', 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 132, in _check_fault self._raise_error(response, body) 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 "[Bond name 'bond_fancy0' does not follow naming criteria. Bond name must begin with the prefix 'bond' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of 'a-z', 'A-Z', '0-9' or '_' characters]". HTTP response code is 400. --------------------- >> 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 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 197, in bond_nics utils.invoke_in_parallel(_bond_nics, range(1, len(hosts) + 1), hosts) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 100, in invoke_in_parallel return vt.join_all() File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics [bond]) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host check_connectivity=True), True, []) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda> check_connectivity=True), True, []) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict check_connectivity=check_connectivity) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks return self._internal_action(action, 'setupnetworks', 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 132, in _check_fault self._raise_error(response, body) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error 'Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6d9320>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\nlago.utils: ERROR: Error while running thread\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics\n [bond])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host\n check_connectivity=True), True, [])\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short\n func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\novirtlago.testlib: ERROR: Unhandled exception in <function <lambda> at 0x7f93ad6a47d0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\nlago.utils: ERROR: Error while running thread\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue\n queue.put({\'return\': func()})\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test-scenarios/003_basic_networking.py", line 194, in _bond_nics\n [bond])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in attach_network_to_host\n check_connectivity=True), True, [])\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short\n func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 234, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 48, in <lambda>\n check_connectivity=True), True, [])\n File "/home/jenkins/workspace/ovirt-system-tests_compat-4.1-suite-master/ovirt-system-tests/compat-4.1-suite-master/test_utils/network_utils_v4.py", line 286, in _setup_host_networks_without_conflict\n check_connectivity=check_connectivity)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 39181, in setup_networks\n return self._internal_action(action, \'setupnetworks\', None, headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait\n return self._code(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 132, in _check_fault\n self._raise_error(response, body)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error\n raise error\nError: Fault reason is "Operation Failed". Fault detail is "[Bond name \'bond_fancy0\' does not follow naming criteria. Bond name must begin with the prefix \'bond\' followed by a number for host compatibility version < 4.3 otherwise the name must be formed of \'a-z\', \'A-Z\', \'0-9\' or \'_\' characters]". HTTP response code is 400.\n--------------------- >> end captured logging << ---------------------'

1 33

[JIRA] (OVIRT-2622) jenkins slave missing KVM support
by Emil Natan (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2622: ------------------------------ Resolution: Won't Fix Status: Done (was: To Do) > jenkins slave missing KVM support > --------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2622) jenkins slave missing KVM support
by Emil Natan (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2622: ------------------------------ Summary: jenkins slave missing KVM support (was: cinteg19.ci.lab.tlv.redhat.com missing KVM support) > jenkins slave missing KVM support > --------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2622) cinteg19.ci.lab.tlv.redhat.com missing KVM support
by Emil Natan (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2622: ------------------------------ Description: 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM 09:02:53 + echo 'options kvm_intel nested=y' 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf 09:02:53 options kvm_intel nested=y 09:02:53 + sudo -n rmmod kvm_intel 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded 09:02:54 + sudo -n modprobe kvm_intel nested=y 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not supported 09:02:54 + is_nested_kvm_enabled 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] 09:02:54 + return 1 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' 09:02:54 + local level=ERROR 09:02:54 + shift 09:02:54 + local 'message=failed to enable nested KVM, aborting' 09:02:54 + local prefix 09:02:54 + [[ 4 -gt 1 ]] 09:02:54 + prefix='global_setup[nested_kvm]' 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting' 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting 09:02:54 + return 1 -- Emil Natan RHV/CNV DevOps was: https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-jenkins_s… 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM 09:02:53 + echo 'options kvm_intel nested=y' 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf 09:02:53 options kvm_intel nested=y 09:02:53 + sudo -n rmmod kvm_intel 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded 09:02:54 + sudo -n modprobe kvm_intel nested=y 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not supported 09:02:54 + is_nested_kvm_enabled 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] 09:02:54 + return 1 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' 09:02:54 + local level=ERROR 09:02:54 + shift 09:02:54 + local 'message=failed to enable nested KVM, aborting' 09:02:54 + local prefix 09:02:54 + [[ 4 -gt 1 ]] 09:02:54 + prefix='global_setup[nested_kvm]' 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting' 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, aborting 09:02:54 + return 1 -- Emil Natan RHV/CNV DevOps > cinteg19.ci.lab.tlv.redhat.com missing KVM support > -------------------------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2622) cinteg19.ci.lab.tlv.redhat.com missing KVM support
by Barak Korren (oVirt JIRA) 12 Dec '18

12 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2622?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2622: ------------------------------------- [~ena(a)redhat.com] this is a DS issue, this is the US jira. Please delete this ticket and open in the right place. > cinteg19.ci.lab.tlv.redhat.com missing KVM support > -------------------------------------------------- > > Key: OVIRT-2622 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2622 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-jenkins_s… > 09:02:53 + echo 'global_setup[nested_kvm] INFO: Enabling nested KVM' > 09:02:53 global_setup[nested_kvm] INFO: Enabling nested KVM > 09:02:53 + echo 'options kvm_intel nested=y' > 09:02:53 + sudo -n tee /etc/modprobe.d/nested.conf > 09:02:53 options kvm_intel nested=y > 09:02:53 + sudo -n rmmod kvm_intel > 09:02:54 rmmod: ERROR: Module kvm_intel is not currently loaded > 09:02:54 + sudo -n modprobe kvm_intel nested=y > 09:02:54 modprobe: ERROR: could not insert 'kvm_intel': Operation not > supported > 09:02:54 + is_nested_kvm_enabled > 09:02:54 + local i_nested_path=/sys/module/kvm_intel/parameters/nested > 09:02:54 + [[ -f /sys/module/kvm_intel/parameters/nested ]] > 09:02:54 + return 1 > 09:02:54 + log ERROR 'failed to enable nested KVM, aborting' > 09:02:54 + local level=ERROR > 09:02:54 + shift > 09:02:54 + local 'message=failed to enable nested KVM, aborting' > 09:02:54 + local prefix > 09:02:54 + [[ 4 -gt 1 ]] > 09:02:54 + prefix='global_setup[nested_kvm]' > 09:02:54 + echo 'global_setup[nested_kvm] ERROR: failed to enable nested > KVM, aborting' > 09:02:54 global_setup[nested_kvm] ERROR: failed to enable nested KVM, > aborting > 09:02:54 + return 1 > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0