- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 804 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Oct '18

23 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/804/ Build Number: 804 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #804 [Galit] Fix stdci.yaml to be able to run poll upstream sources ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fde909da230> 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_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 253, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 38104, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get 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 208, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault body = self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 850, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 890, in _check_content_type raise Error(msg) Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML --------------------- >> 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 "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 228, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 275, 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 278, in assert_true_within assert_equals_within(func, True, timeout, 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_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 253, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 38104, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get 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 208, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault body = self._internal_read_body(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body self._connection.check_xml_content_type(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 850, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 890, in _check_content_type raise Error(msg) 'The response content type \'text/html; charset=iso-8859-1\' isn\'t the expected XML\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7fde909da230>\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_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 253, in _host_is_up_4\n host_obj = host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 38104, in get\n return self._internal_get(headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get\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 208, in callback\n self._check_fault(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 130, in _check_fault\n body = self._internal_read_body(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 316, in _internal_read_body\n self._connection.check_xml_content_type(response)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 850, in check_xml_content_type\n response.headers\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 890, in _check_content_type\n raise Error(msg)\nError: The response content type \'text/html; charset=iso-8859-1\' isn\'t the expected XML\n--------------------- >> end captured logging << ---------------------'

1 8

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 411 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Oct '18

23 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/411/ Build Number: 411 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #411 [Galit] Update the config for poll u/s sources ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 010_local_maintenance_cli.local_maintenance Error Message: 143 -------------------- >> begin captured logging << -------------------- root: INFO: * Waiting For System Stability... lago.ssh: DEBUG: start task:461f166d-b3cb-4766-af33-4319bd3b5227:Get ssh client for lago-he-node-ng-suite-4-2-host-1: lago.ssh: DEBUG: end task:461f166d-b3cb-4766-af33-4319bd3b5227:Get ssh client for lago-he-node-ng-suite-4-2-host-1: lago.ssh: DEBUG: Running 5e792150 on lago-he-node-ng-suite-4-2-host-1: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 5e792150 on lago-he-node-ng-suite-4-2-host-1 returned with 0 lago.ssh: DEBUG: Command 5e792150 on lago-he-node-ng-suite-4-2-host-1 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3933 (Thu Oct 18 01:44:27 2018)\nhost-id=1\nscore=3400\nvm_conf_refresh_time=3933 (Thu Oct 18 01:44:28 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineUp\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Up"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "f7c0dd5c", "local_conf_timestamp": 3933, "host-ts": 3933}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3935 (Thu Oct 18 01:44:29 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3935 (Thu Oct 18 01:44:29 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "da25a075", "local_conf_timestamp": 3935, "host-ts": 3935}, "global_maintenance": false} lago.ssh: DEBUG: start task:a64ae178-4ca1-4b6a-b5a6-e4250fe83398:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:a64ae178-4ca1-4b6a-b5a6-e4250fe83398:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 5f815572 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --set-maintenance --mode=local lago.ssh: DEBUG: Command 5f815572 on lago-he-node-ng-suite-4-2-host-0 returned with 0 root: INFO: * Waiting for engine to migrate... lago.ssh: DEBUG: start task:23a6c556-e234-43d1-8313-4612bd35fdf0:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:23a6c556-e234-43d1-8313-4612bd35fdf0:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 60b78506 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 60b78506 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 60b78506 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3943 (Thu Oct 18 01:44:38 2018)\nhost-id=1\nscore=3400\nvm_conf_refresh_time=3943 (Thu Oct 18 01:44:38 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineUp\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Up"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "8f671722", "local_conf_timestamp": 3943, "host-ts": 3943}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3935 (Thu Oct 18 01:44:29 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3935 (Thu Oct 18 01:44:29 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "da25a075", "local_conf_timestamp": 3935, "host-ts": 3935}, "global_maintenance": false} lago.ssh: DEBUG: start task:080e3a23-a075-43dd-895c-00855470de8a:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:080e3a23-a075-43dd-895c-00855470de8a:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 67d368b4 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 67d368b4 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 67d368b4 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3953 (Thu Oct 18 01:44:47 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3953 (Thu Oct 18 01:44:47 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Up"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "706f0031", "local_conf_timestamp": 3953, "host-ts": 3953}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3945 (Thu Oct 18 01:44:39 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3945 (Thu Oct 18 01:44:39 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "c7f55d6e", "local_conf_timestamp": 3945, "host-ts": 3945}, "global_maintenance": false} lago.ssh: DEBUG: start task:592ee562-ac13-4dee-9eeb-8e72bbe78ced:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:592ee562-ac13-4dee-9eeb-8e72bbe78ced:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 6bf19f06 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 6bf19f06 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 6bf19f06 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3963 (Thu Oct 18 01:44:58 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3963 (Thu Oct 18 01:44:58 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "6263fdaa", "local_conf_timestamp": 3963, "host-ts": 3963}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3955 (Thu Oct 18 01:44:50 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3956 (Thu Oct 18 01:44:50 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "5abaf3d1", "local_conf_timestamp": 3956, "host-ts": 3955}, "global_maintenance": false} lago.ssh: DEBUG: start task:3aac038b-901e-4bca-8616-7dae3ce335b0:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:3aac038b-901e-4bca-8616-7dae3ce335b0:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 6ef7539e on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 6ef7539e on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 6ef7539e on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3963 (Thu Oct 18 01:44:58 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3963 (Thu Oct 18 01:44:58 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "6263fdaa", "local_conf_timestamp": 3963, "host-ts": 3963}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3955 (Thu Oct 18 01:44:50 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3956 (Thu Oct 18 01:44:50 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "5abaf3d1", "local_conf_timestamp": 3956, "host-ts": 3955}, "global_maintenance": false} lago.ssh: DEBUG: start task:a8248fe7-4e2c-455d-b5ec-b1954bf41a8e:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:a8248fe7-4e2c-455d-b5ec-b1954bf41a8e:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 71ed0dfa on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 71ed0dfa on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 71ed0dfa on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3973 (Thu Oct 18 01:45:08 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3974 (Thu Oct 18 01:45:08 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "523456cb", "local_conf_timestamp": 3974, "host-ts": 3973}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3965 (Thu Oct 18 01:44:59 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3965 (Thu Oct 18 01:44:59 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "b84596fc", "local_conf_timestamp": 3965, "host-ts": 3965}, "global_maintenance": false} lago.ssh: DEBUG: start task:65b6000b-8e80-4dee-af83-a6a74c034238:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:65b6000b-8e80-4dee-af83-a6a74c034238:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 74df0478 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 74df0478 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 74df0478 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3973 (Thu Oct 18 01:45:08 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3974 (Thu Oct 18 01:45:08 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "523456cb", "local_conf_timestamp": 3974, "host-ts": 3973}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3965 (Thu Oct 18 01:44:59 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3965 (Thu Oct 18 01:44:59 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "b84596fc", "local_conf_timestamp": 3965, "host-ts": 3965}, "global_maintenance": false} lago.ssh: DEBUG: start task:847d9012-2456-4e12-b2f9-c7e4da9c4ff7:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:847d9012-2456-4e12-b2f9-c7e4da9c4ff7:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 77d8a918 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 77d8a918 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 77d8a918 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3983 (Thu Oct 18 01:45:17 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3983 (Thu Oct 18 01:45:17 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "41e59273", "local_conf_timestamp": 3983, "host-ts": 3983}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3975 (Thu Oct 18 01:45:09 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3975 (Thu Oct 18 01:45:09 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "bc0369f9", "local_conf_timestamp": 3975, "host-ts": 3975}, "global_maintenance": false} lago.ssh: DEBUG: start task:dd6b5da4-d22b-4284-85d5-dfe9a51ee00c:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:dd6b5da4-d22b-4284-85d5-dfe9a51ee00c:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 7ac56292 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 7ac56292 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 7ac56292 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3983 (Thu Oct 18 01:45:17 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3983 (Thu Oct 18 01:45:17 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "41e59273", "local_conf_timestamp": 3983, "host-ts": 3983}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3975 (Thu Oct 18 01:45:09 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3975 (Thu Oct 18 01:45:09 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "bc0369f9", "local_conf_timestamp": 3975, "host-ts": 3975}, "global_maintenance": false} lago.ssh: DEBUG: start task:315c897e-fc06-484c-a036-617859dbb2ec:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:315c897e-fc06-484c-a036-617859dbb2ec:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 7db577e4 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 7db577e4 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 7db577e4 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3993 (Thu Oct 18 01:45:28 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3994 (Thu Oct 18 01:45:28 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "71b23912", "local_conf_timestamp": 3994, "host-ts": 3993}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3985 (Thu Oct 18 01:45:19 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3985 (Thu Oct 18 01:45:19 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "83e46cca", "local_conf_timestamp": 3985, "host-ts": 3985}, "global_maintenance": false} lago.ssh: DEBUG: start task:c5f00620-37e4-4d82-b99e-e9ac42e3e145:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: end task:c5f00620-37e4-4d82-b99e-e9ac42e3e145:Get ssh client for lago-he-node-ng-suite-4-2-host-0: lago.ssh: DEBUG: Running 81550626 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json lago.ssh: DEBUG: Command 81550626 on lago-he-node-ng-suite-4-2-host-0 returned with 0 lago.ssh: DEBUG: Command 81550626 on lago-he-node-ng-suite-4-2-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3993 (Thu Oct 18 01:45:28 2018)\nhost-id=1\nscore=3000\nvm_conf_refresh_time=3994 (Thu Oct 18 01:45:28 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineMigratingAway\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "71b23912", "local_conf_timestamp": 3994, "host-ts": 3993}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=3985 (Thu Oct 18 01:45:19 2018)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=3985 (Thu Oct 18 01:45:19 2018)\nconf_on_shared_storage=True\nmaintenance=False\nstate=EngineDown\nstopped=False\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "83e46cca", "local_conf_timestamp": 3985, "host-ts": 3985}, "global_maintenance": false} cli: DEBUG: signal 15 was caught --------------------- >> 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 "/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-4.2/ovirt-system-tests/he-node-ng-suite-4.2/test-scenarios/010_local_maintenance_cli.py", line 125, in local_maintenance _wait_for_engine_migration(host, he_index, "bad", "Migration Destination") File "/home/jenkins/workspace/ovirt-system-tests_he-node-ng-suite-4.2/ovirt-system-tests/he-node-ng-suite-4.2/test-scenarios/010_local_maintenance_cli.py", line 36, in _wait_for_engine_migration testlib.assert_true_within_long(lambda: _get_he_status(host) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 246, in assert_equals_within time.sleep(3) File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 922, in exit_handler sys.exit(128 + signum) '143\n-------------------- >> begin captured logging << --------------------\nroot: INFO: * Waiting For System Stability...\nlago.ssh: DEBUG: start task:461f166d-b3cb-4766-af33-4319bd3b5227:Get ssh client for lago-he-node-ng-suite-4-2-host-1:\nlago.ssh: DEBUG: end task:461f166d-b3cb-4766-af33-4319bd3b5227:Get ssh client for lago-he-node-ng-suite-4-2-host-1:\nlago.ssh: DEBUG: Running 5e792150 on lago-he-node-ng-suite-4-2-host-1: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 5e792150 on lago-he-node-ng-suite-4-2-host-1 returned with 0\nlago.ssh: DEBUG: Command 5e792150 on lago-he-node-ng-suite-4-2-host-1 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3933 (Thu Oct 18 01:44:27 2018)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3933 (Thu Oct 18 01:44:28 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineUp\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Up"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "f7c0dd5c", "local_conf_timestamp": 3933, "host-ts": 3933}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3935 (Thu Oct 18 01:44:29 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3935 (Thu Oct 18 01:44:29 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "da25a075", "local_conf_timestamp": 3935, "host-ts": 3935}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:a64ae178-4ca1-4b6a-b5a6-e4250fe83398:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:a64ae178-4ca1-4b6a-b5a6-e4250fe83398:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 5f815572 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --set-maintenance --mode=local\nlago.ssh: DEBUG: Command 5f815572 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nroot: INFO: * Waiting for engine to migrate...\nlago.ssh: DEBUG: start task:23a6c556-e234-43d1-8313-4612bd35fdf0:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:23a6c556-e234-43d1-8313-4612bd35fdf0:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 60b78506 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 60b78506 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 60b78506 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3943 (Thu Oct 18 01:44:38 2018)\\nhost-id=1\\nscore=3400\\nvm_conf_refresh_time=3943 (Thu Oct 18 01:44:38 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineUp\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Up"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "8f671722", "local_conf_timestamp": 3943, "host-ts": 3943}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3935 (Thu Oct 18 01:44:29 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3935 (Thu Oct 18 01:44:29 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "da25a075", "local_conf_timestamp": 3935, "host-ts": 3935}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:080e3a23-a075-43dd-895c-00855470de8a:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:080e3a23-a075-43dd-895c-00855470de8a:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 67d368b4 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 67d368b4 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 67d368b4 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3953 (Thu Oct 18 01:44:47 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3953 (Thu Oct 18 01:44:47 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Up"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "706f0031", "local_conf_timestamp": 3953, "host-ts": 3953}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3945 (Thu Oct 18 01:44:39 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3945 (Thu Oct 18 01:44:39 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "c7f55d6e", "local_conf_timestamp": 3945, "host-ts": 3945}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:592ee562-ac13-4dee-9eeb-8e72bbe78ced:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:592ee562-ac13-4dee-9eeb-8e72bbe78ced:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 6bf19f06 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 6bf19f06 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 6bf19f06 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3963 (Thu Oct 18 01:44:58 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3963 (Thu Oct 18 01:44:58 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "6263fdaa", "local_conf_timestamp": 3963, "host-ts": 3963}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3955 (Thu Oct 18 01:44:50 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3956 (Thu Oct 18 01:44:50 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "5abaf3d1", "local_conf_timestamp": 3956, "host-ts": 3955}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:3aac038b-901e-4bca-8616-7dae3ce335b0:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:3aac038b-901e-4bca-8616-7dae3ce335b0:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 6ef7539e on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 6ef7539e on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 6ef7539e on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3963 (Thu Oct 18 01:44:58 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3963 (Thu Oct 18 01:44:58 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "6263fdaa", "local_conf_timestamp": 3963, "host-ts": 3963}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3955 (Thu Oct 18 01:44:50 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3956 (Thu Oct 18 01:44:50 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "5abaf3d1", "local_conf_timestamp": 3956, "host-ts": 3955}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:a8248fe7-4e2c-455d-b5ec-b1954bf41a8e:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:a8248fe7-4e2c-455d-b5ec-b1954bf41a8e:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 71ed0dfa on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 71ed0dfa on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 71ed0dfa on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3973 (Thu Oct 18 01:45:08 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3974 (Thu Oct 18 01:45:08 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "523456cb", "local_conf_timestamp": 3974, "host-ts": 3973}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3965 (Thu Oct 18 01:44:59 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3965 (Thu Oct 18 01:44:59 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "b84596fc", "local_conf_timestamp": 3965, "host-ts": 3965}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:65b6000b-8e80-4dee-af83-a6a74c034238:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:65b6000b-8e80-4dee-af83-a6a74c034238:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 74df0478 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 74df0478 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 74df0478 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3973 (Thu Oct 18 01:45:08 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3974 (Thu Oct 18 01:45:08 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "523456cb", "local_conf_timestamp": 3974, "host-ts": 3973}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3965 (Thu Oct 18 01:44:59 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3965 (Thu Oct 18 01:44:59 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "b84596fc", "local_conf_timestamp": 3965, "host-ts": 3965}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:847d9012-2456-4e12-b2f9-c7e4da9c4ff7:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:847d9012-2456-4e12-b2f9-c7e4da9c4ff7:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 77d8a918 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 77d8a918 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 77d8a918 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3983 (Thu Oct 18 01:45:17 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3983 (Thu Oct 18 01:45:17 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "41e59273", "local_conf_timestamp": 3983, "host-ts": 3983}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3975 (Thu Oct 18 01:45:09 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3975 (Thu Oct 18 01:45:09 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "bc0369f9", "local_conf_timestamp": 3975, "host-ts": 3975}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:dd6b5da4-d22b-4284-85d5-dfe9a51ee00c:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:dd6b5da4-d22b-4284-85d5-dfe9a51ee00c:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 7ac56292 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 7ac56292 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 7ac56292 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3983 (Thu Oct 18 01:45:17 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3983 (Thu Oct 18 01:45:17 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "41e59273", "local_conf_timestamp": 3983, "host-ts": 3983}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3975 (Thu Oct 18 01:45:09 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3975 (Thu Oct 18 01:45:09 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "bc0369f9", "local_conf_timestamp": 3975, "host-ts": 3975}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:315c897e-fc06-484c-a036-617859dbb2ec:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:315c897e-fc06-484c-a036-617859dbb2ec:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 7db577e4 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 7db577e4 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 7db577e4 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3993 (Thu Oct 18 01:45:28 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3994 (Thu Oct 18 01:45:28 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "71b23912", "local_conf_timestamp": 3994, "host-ts": 3993}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3985 (Thu Oct 18 01:45:19 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3985 (Thu Oct 18 01:45:19 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "83e46cca", "local_conf_timestamp": 3985, "host-ts": 3985}, "global_maintenance": false}\n\nlago.ssh: DEBUG: start task:c5f00620-37e4-4d82-b99e-e9ac42e3e145:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: end task:c5f00620-37e4-4d82-b99e-e9ac42e3e145:Get ssh client for lago-he-node-ng-suite-4-2-host-0:\nlago.ssh: DEBUG: Running 81550626 on lago-he-node-ng-suite-4-2-host-0: hosted-engine --vm-status --json\nlago.ssh: DEBUG: Command 81550626 on lago-he-node-ng-suite-4-2-host-0 returned with 0\nlago.ssh: DEBUG: Command 81550626 on lago-he-node-ng-suite-4-2-host-0 output:\n {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3993 (Thu Oct 18 01:45:28 2018)\\nhost-id=1\\nscore=3000\\nvm_conf_refresh_time=3994 (Thu Oct 18 01:45:28 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineMigratingAway\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-0", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "Migration Source"}, "score": 3000, "stopped": false, "maintenance": false, "crc32": "71b23912", "local_conf_timestamp": 3994, "host-ts": 3993}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\\nmetadata_feature_version=1\\ntimestamp=3985 (Thu Oct 18 01:45:19 2018)\\nhost-id=2\\nscore=3400\\nvm_conf_refresh_time=3985 (Thu Oct 18 01:45:19 2018)\\nconf_on_shared_storage=True\\nmaintenance=False\\nstate=EngineDown\\nstopped=False\\n", "hostname": "lago-he-node-ng-suite-4-2-host-1", "host-id": 2, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "down", "detail": "Migration Destination"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "83e46cca", "local_conf_timestamp": 3985, "host-ts": 3985}, "global_maintenance": false}\n\ncli: DEBUG: signal 15 was caught\n--------------------- >> end captured logging << ---------------------'

1 17

[JIRA] (OVIRT-2558) containerize more bare metals
by Evgheni Dereveanchin (oVirt JIRA) 23 Oct '18

23 Oct '18

Evgheni Dereveanchin created OVIRT-2558: ------------------------------------------- Summary: containerize more bare metals Key: OVIRT-2558 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2558 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra The build queue on the Jenkins is growing and we still have two larger bare metals under-utilized as they run just a single Lago instance at a time: ovirt-srv07 and ovirt-srv08 I've offlined them so that they can be containerized and run up to 7 CI suites at the same time, same as we have on ovirt-srv04-06 at the moment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 95011, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Oct '18

23 Oct '18

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

2 1

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 92 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Oct '18

23 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build Number: 92 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #92 [Yuval Turgeman] stdci: move build-artifacts to a v1 job ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2557) upgrade jenkins.ovirt.org to 2.138.2 LTS
by Evgheni Dereveanchin (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2557?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2557: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade jenkins.ovirt.org to 2.138.2 LTS > ---------------------------------------- > > Key: OVIRT-2557 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2557 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Jenkins 2.138.2 LTS is out, our instance needs to be updated. > https://jenkins.io/changelog-stable/ > Plugin security updates were also released so we should bump versions, too -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2557) upgrade jenkins.ovirt.org to 2.138.2 LTS
by Evgheni Dereveanchin (oVirt JIRA) 23 Oct '18

23 Oct '18

Evgheni Dereveanchin created OVIRT-2557: ------------------------------------------- Summary: upgrade jenkins.ovirt.org to 2.138.2 LTS Key: OVIRT-2557 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2557 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Jenkins 2.138.2 LTS is out, our instance needs to be updated. https://jenkins.io/changelog-stable/ Plugin security updates were also released so we should bump versions, too -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Gal Ben Haim (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2556: ------------------------------------- [~lbednar] FYI > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Gal Ben Haim (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2556: ------------------------------------- I've killed the old STDCI container and spawned a new one instead. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources
by Evgheni Dereveanchin (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2555: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 95003, 3 (pthreading) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Oct '18

23 Oct '18

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

1 0

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2555: ---------------------------------- I was able to wget and repoquery the package: https://pastebin.com/d0ALuqGF > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Roman Mohr (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2556: ----------------------------------- Ok, let me see if it looks better now. For reference here a very bad run https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2347/arti… from https://github.com/kubevirt/kubevirt/pull/1627. Retriggered test runs there now. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Gal Ben Haim (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2556: ------------------------------------- All the jobs that failed run on `ovirt-srv04.phx.ovirt.org-container-1`. For the meanwhile, I marked this slave offline in Jenkins. Looks like the docker daemon in this slave runs correctly, so further investigation is needed. > kubevirt test runs and nested docker issue > ------------------------------------------ > > Key: OVIRT-2556 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Hi, > we see a lot of tests which fail with during the setup [1] : > ``` > /usr/bin/docker-current: Error response from daemon: grpc: the > connection is unavailable. > time="2018-10-23T07:17:55Z" level=error msg="error getting events from > daemon: context canceled" > ``` > It looks like the docker daemon may not run properly. > Best Regards, > Roman > [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 95058,2 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 23 Oct '18

23 Oct '18

Change 95058,2 (cockpit-ovirt) 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/95058/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10903/

2 1

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2555: ---------------------------------- https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10903/ > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue
by Roman Mohr (oVirt JIRA) 23 Oct '18

23 Oct '18

Roman Mohr created OVIRT-2556: --------------------------------- Summary: kubevirt test runs and nested docker issue Key: OVIRT-2556 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2556 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roman Mohr Assignee: infra Hi, we see a lot of tests which fail with during the setup [1] : ``` /usr/bin/docker-current: Error response from daemon: grpc: the connection is unavailable. time="2018-10-23T07:17:55Z" level=error msg="error getting events from daemon: context canceled" ``` It looks like the docker daemon may not run properly. Best Regards, Roman [1] https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/2344//art… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #2063
by jenkins＠jenkins.phx.ovirt.org 23 Oct '18

23 Oct '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision dcca3490534c35726a94ed81749344ef764e31ac (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f dcca3490534c35726a94ed81749344ef764e31ac Commit message: "Revert "Removed ovirt-provider-ovn v1 jobs"" > git rev-list --no-walk dcca3490534c35726a94ed81749344ef764e31ac # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6570870427910087477.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/epel-el6 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/epel-el6' Build step 'Execute shell' marked build as failure

1 2

[CQ]: b98ef7a (ovirt-ansible-disaster-recovery) failed "ovirt-master" system tests
by oVirt Jenkins 23 Oct '18

23 Oct '18

Change b98ef7a (ovirt-ansible-disaster-recovery) 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://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/b98ef7af9ae… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10901/

2 1

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2555: ---------------------------------- https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10901/ > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 95011, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Oct '18

23 Oct '18

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

2 1

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2555: ---------------------------------- second failure for otopi: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10898/ > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JIRA] (OVIRT-2555) failures on ovirt-master failed due to access to resources
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2555?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2555: ----------------------------- Summary: failures on ovirt-master failed due to access to resources (was: ovirt-ansible-v2v-conversion-host on ovirt-master failed due to access to resources ) > failures on ovirt-master failed due to access to resources > ----------------------------------------------------------- > > Key: OVIRT-2555 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ > [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 74b0e9e (ovirt-ansible-v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Oct '18

23 Oct '18

A system test invoked by the "ovirt-master" change queue including change 74b0e9e (ovirt-ansible-v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 1e8001a (ovirt-ansible-v2v- conversion-host) 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 1e8001a (ovirt-ansible-v2v- conversion-host) 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://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/74b0e9eec… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/1e8001a77… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/

2 1

[JIRA] (OVIRT-2555) ovirt-ansible-v2v-conversion-host on ovirt-master failed due to access to resources
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

Dafna Ron created OVIRT-2555: -------------------------------- Summary: ovirt-ansible-v2v-conversion-host on ovirt-master failed due to access to resources Key: OVIRT-2555 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2555 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra 21:38:01 [upgrade-from-release-suite.el7.x86_64] RuntimeError: Failed to run reposync 3 times for repoid: ovirt-4.2-tested-el7, aborting. https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10896/ [~ederevea] can you please take a look to see if we have issues with the server? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[CQ]: 95003, 3 (pthreading) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Oct '18

23 Oct '18

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

2 1

[JIRA] (OVIRT-2554) failure in master pthreading project on test 004_basic_sanity.next_run_unplug_cpu with no clear logs
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

Dafna Ron created OVIRT-2554: -------------------------------- Summary: failure in master pthreading project on test 004_basic_sanity.next_run_unplug_cpu with no clear logs Key: OVIRT-2554 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2554 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest we had a failure in master on test 004_basic_sanity.next_run_unplug_cpu for project pthreading and there are no logs that can help me debug the issue. There are post-suite-sigterm but there are no logs in there that can help me understand what happened. [~gbenhaim(a)redhat.com] can you please look at this failure? https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10892/artifa… I re-triggered the last project's change to make sure it passes but I am not sure how to debug this failure. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

[JENKINS] Failed to setup proejct kubevirt_common-templates_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Oct '18

23 Oct '18

Failed to run project_setup.sh for: #130 common-templates [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 ovirt-srv04.phx.ovirt.org-container-1.

1 2

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

23 Oct '18

Failed to run project_setup.sh for: #2347 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2347 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2347 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2347 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2347 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2347 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-el7-x86_64 - Build # 87 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Oct '18

23 Oct '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7… Build Number: 87 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #87 [Yuval Turgeman] stdci: move build-artifacts to a v1 job ----------------- Failed Tests: ----------------- No tests ran.

1 5

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2346 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2345 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2549?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2549: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > master ovirt-engine fails on missing package > -------------------------------------------- > > Key: OVIRT-2549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2549 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_packages > > logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… > change not related: https://gerrit.ovirt.org/#/c/94567/2 > error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2345 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

[JIRA] (OVIRT-2549) master ovirt-engine fails on missing package
by Dafna Ron (oVirt JIRA) 23 Oct '18

23 Oct '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2549?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2549: ---------------------------------- thanks you [~sbonazzo(a)redhat.com] This issue is resolved. > master ovirt-engine fails on missing package > -------------------------------------------- > > Key: OVIRT-2549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2549 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_packages > > logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10643/artifa… > change not related: https://gerrit.ovirt.org/#/c/94567/2 > error from deploy host: https://pastebin.com/CfLTRe5R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2345 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2345 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0

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

23 Oct '18

Failed to run project_setup.sh for: #2345 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 ovirt-srv04.phx.ovirt.org-container-1.

1 0