- Infra - oVirt List Archives

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

29 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92535,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 92567,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/92535/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92567/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8439/

1 0

[CQ]: 92572, 2 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jun '18

29 Jun '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 285 - Failure!
by jenkins＠jenkins.phx.ovirt.org 29 Jun '18

29 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 285 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #285 [Gal Ben Haim] Make sure that crond is installed and running ----------------- Failed Tests: ----------------- All tests passed

1 2

[CQ]: 92446, 8 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jun '18

29 Jun '18

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

1 0

[CQ]: 92488, 3 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jun '18

29 Jun '18

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

1 0

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

29 Jun '18

A system test invoked by the "ovirt-master" change queue including change 90352,22 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 92567,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/90352/22 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92567/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8419/

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 76 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '18

28 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/76/ Build Number: 76 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #76 [Gal Ben Haim] Make sure that crond is installed and running ----------------- Failed Tests: ----------------- All tests passed

1 1

[CQ]: 92544, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jun '18

28 Jun '18

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

1 0

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

28 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/301/ Build Number: 301 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #301 [Gal Ben Haim] Make sure that crond is installed and running ----------------- 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 0x7fd5c5b205f0> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, 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 849, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, 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 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 229, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 273, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, 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 849, in check_xml_content_type response.headers File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, 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 0x7fd5c5b205f0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/002_bootstrap.py", line 254, in _host_is_up_4\n host_obj = host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36846, 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 849, in check_xml_content_type\n response.headers\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 889, 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 2

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

28 Jun '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/74/ Build Number: 74 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #74 [Gal Ben Haim] Make sure that crond is installed and running [Barak Korren] Install JJB via PIP instead of YUM [Barak Korren] Clean deprecation warning from JJB output [Barak Korren] Upgrade JJB to 1.6.2 ----------------- Failed Tests: ----------------- All tests passed

1 3

[JIRA] (OVIRT-2267) POC - Try to run Lago inside a container
by Gal Ben Haim (oVirt JIRA) 28 Jun '18

28 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2267?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2267: -------------------------------- Status: In Progress (was: To Do) > POC - Try to run Lago inside a container > ---------------------------------------- > > Key: OVIRT-2267 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2267 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Lago > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2267) POC - Try to run Lago inside a container
by Gal Ben Haim (oVirt JIRA) 28 Jun '18

28 Jun '18

Gal Ben Haim created OVIRT-2267: ----------------------------------- Summary: POC - Try to run Lago inside a container Key: OVIRT-2267 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2267 Project: oVirt - virtualization made easy Issue Type: Bug Components: Lago Reporter: Gal Ben Haim Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2267) POC - Try to run Lago inside a container
by Gal Ben Haim (oVirt JIRA) 28 Jun '18

28 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2267?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2267: -------------------------------- Epic Link: OVIRT-2246 > POC - Try to run Lago inside a container > ---------------------------------------- > > Key: OVIRT-2267 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2267 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Lago > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 92545,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 28 Jun '18

28 Jun '18

Change 92545,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/92545/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8407/

1 0

[JIRA] (OVIRT-2266) docker_cleanup.py can't run without a whitelist value
by Ehud Yonasi (oVirt JIRA) 28 Jun '18

28 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2266?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2266: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > docker_cleanup.py can't run without a whitelist value > ----------------------------------------------------- > > Key: OVIRT-2266 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2266 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > > there is a bug running docker_cleanup.py without args, because whitelisted images expects a not null value. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2266) docker_cleanup.py can't run without a whitelist value
by Ehud Yonasi (oVirt JIRA) 28 Jun '18

28 Jun '18

Ehud Yonasi created OVIRT-2266: ---------------------------------- Summary: docker_cleanup.py can't run without a whitelist value Key: OVIRT-2266 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2266 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Ehud Yonasi Assignee: infra there is a bug running docker_cleanup.py without args, because whitelisted images expects a not null value. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 91785, 3 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 28 Jun '18

28 Jun '18

Change 91785,3 (ovirt-hosted-engine-setup) 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/91785/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8402/

1 0

[oVirt Jenkins] ovirt-node-ng_master_build-artifacts-el7-x86_64 - Build # 839 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '18

28 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… Build Number: 839 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #839 [Evgheni Dereveanchin] load OVS module from global_setup [Sandro Bonazzola] ovirt-engine-sdk: drop ppc64le on fedora [Vojtech Szocs] Add ovirt-engine-ui-extensions to stdci v2 [Daniel Belenky] Move stdci runner code to a shared library [Daniel Belenky] Use stdci_runner lib in ovirt change-queue tester [Ryan Barry] kickstart: let VDSM reconfigure itself ----------------- Failed Tests: ----------------- No tests ran.

1 1

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]
by Dafna Ron 28 Jun '18

28 Jun '18

Hi, We had a failure in test 098_ovirt_provider_ovn.use_ovn_provider. Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/92567/ - packaging: Add python-netaddr requirement I actually think from the error its because of changes made to multiqueues https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to consider vmBase.multiQueuesEnabled attribute https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for calculating how many queues asign per vnic https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to VmBase https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues Enabled' to the relevant mappers https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues Enabled' to vm dialog Alona, can you please take a look? *Link to Job:* *http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/>Link to all logs:https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/ar… <https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/artifac…>(Relevant) error snippet from the log: <error>* *eng**ine: * 2018-06-27 13:59:25,976-04 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Command 'GetAllVmStatsVDSCommand(HostName = lago-basic-suite-master-host-1, VdsIdVDSCommandParametersBase:{hostId='d9094c95-3275-4616-b4c2-815e753bcfed'})' execution failed: VDSGenericException: VDSNetworkException: Broken pipe 2018-06-27 13:59:25,977-04 DEBUG [org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil] (EE-ManagedThreadFactory-engine-Thread-442) [] Executing task: EE-ManagedThreadFactory-engine-Thread-442 2018-06-27 13:59:25,977-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engine-Thread-442) [] method: getVdsManager, params: [d9094c95-3275-4616-b4c2-815e753bcfed], timeElapsed: 0ms 2018-06-27 13:59:25,977-04 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedThreadFactory-engine-Thread-442) [] Host 'lago-basic-suite-master-host-1' is not responding. 2018-06-27 13:59:25,979-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-63) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM lago-basic-suite-master-host-1 command GetStatsAsyncVDS failed: Broken pipe 2018-06-27 13:59:25,976-04 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: VDSGenericException: VDSNetworkException: Broken pipe at org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:189) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand.executeVdsBrokerCommand(GetAllVmStatsVDSCommand.java:23) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:399) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor270.invoke(Unknown Source) [:1.8.0_171] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:49) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:77) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source) [:1.8.0_171] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.VmsStatisticsFetcher.poll(VmsStatisticsFetcher.java:29) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.VmsListFetcher.fetch(VmsListFetcher.java:49) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher.poll(PollVmStatsRefresher.java:44) [vdsbroker.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_171] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_171] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) [javax.enterprise.concurrent-1.0.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:78) 2018-06-27 13:59:25,984-04 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetAllVmStatsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] FINISH, GetAllVmStatsVDSCommand, return: , log id: 56d99e77 2018-06-27 13:59:25,984-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] method: runVdsCommand, params: [GetAllVmStats, VdsIdVDSCommandParametersBase:{hostId='d9094c95-3275-4616-b4c2-815e753bcfed'}], timeElapsed: 1497ms 2018-06-27 13:59:25,984-04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedThreadFactory-engineScheduled-Thread-80) [] Failed to fetch vms info for host 'lago-basic-suite-master-host-1' - skipping VMs monitoring. *vdsm: 2018-06-27 14:10:17,314-0400 INFO (jsonrpc/7) [virt.vm] (vmId='b8a11304-07e3-4e64-af35-7421be780d5b') Hotunplug NIC xml: <?xml version='1.0' encoding='utf-8'?><interface type="bridge"> <address bus="0x00" domain="0x0000" function="0x0" slot="0x0b" type="pci" /> <mac address="00:1a:4a:16:01:0e" /> <model type="virtio" /> <source bridge="network_1" /> <link state="up" /> <driver name="vhost" queues="" /> <alias name="ua-3c77476f-f194-476a-8412-d76a9e58d1f9" /></interface> (vm:3321)2018-06-27 14:10:17,328-0400 ERROR (jsonrpc/7) [virt.vm] (vmId='b8a11304-07e3-4e64-af35-7421be780d5b') Hotunplug failed (vm:3353)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 3343, in hotunplugNic self._dom.detachDevice(nicXml) File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 99, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 93, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1177, in detachDevice if ret == -1: raise libvirtError ('virDomainDetachDevice() failed', dom=self)libvirtError: 'queues' attribute must be positive number: 2018-06-27 14:10:17,345-0400 DEBUG (jsonrpc/7) [api] FINISH hotunplugNic response={'status': {'message': "'queues' attribute must be positive number: ", 'code': 50}} (api:136)2018-06-27 14:10:17,346-0400 INFO (jsonrpc/7) [api.virt] FINISH hotunplugNic return={'status': {'message': "'queues' attribute must be positive number: ", 'code': 50}} from=::ffff:192.168.201.4,32976, flow_id=ecb6652, vmId=b8a11304-07e3-4e64-af35-7421be780d5b (api:53)2018-06-27 14:10:17,346-0400 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call VM.hotunplugNic failed (error 50) in 0.07 seconds (__init__:311)2018-06-27 14:10:19,244-0400 DEBUG (qgapoller/2) [vds] Not sending QEMU-GA command 'guest-get-users' to vm_id='b8a11304-07e3-4e64-af35-7421be780d5b', command is not supported (qemuguestagent:192)2018-06-27 14:10:20,038-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Calling 'Host.getAllVmStats' in bridge with {} (__init__:328)2018-06-27 14:10:20,038-0400 INFO (jsonrpc/1) [api.host] START getAllVmStats() from=::1,48032 (api:47)2018-06-27 14:10:20,041-0400 INFO (jsonrpc/1) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,48032 (api:53)2018-06-27 14:10:20,043-0400 DEBUG (jsonrpc/1) [jsonrpc.JsonRpcServer] Return 'Host.getAllVmStats' in bridge with (suppressed) (__init__:355)2018-06-27 14:10:20,043-0400 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:311)2018-06-27 14:10:20,057-0400 DEBUG (jsonrpc/6) [jsonrpc.JsonRpcServer] Calling 'Host.getAllVmIoTunePolicies' in bridge with {} (__init__:328)2018-06-27 14:10:20,058-0400 INFO (jsonrpc/6) [api.host] START getAllVmIoTunePolicies() from=::1,48032 (api:47)2018-06-27 14:10:20,058-0400 INFO (jsonrpc/6) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'message': 'Done', 'code': 0}, 'io_tune_policies_dict': {'b8a11304-07e3-4e64-af35-7421be780d5b': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/blockSD/cf23ceeb-81a3-4714-85a0-c6ddd1e024da/images/650fe4ae-47a1-4f2d-9cba-1617a8c868c3/03e75c3c-24e7-4e68-a6f1-21728aaaa73e', 'name': 'vda'}]}}} from=::1,48032 (api:53)2018-06-27 14:10:20,059-0400 DEBUG (jsonrpc/6) [jsonrpc.JsonRpcServer] Return 'Host.getAllVmIoTunePolicies' in bridge with {'b8a11304-07e3-4e64-af35-7421be780d5b': {'policy': [], 'current_values': [{'ioTune': {'write_bytes_sec': 0L, 'total_iops_sec': 0L, 'read_iops_sec': 0L, 'read_bytes_sec': 0L, 'write_iops_sec': 0L, 'total_bytes_sec': 0L}, 'path': '/rhev/data-center/mnt/blockSD/cf23ceeb-81a3-4714-85a0-c6ddd1e024da/images/650fe4ae-47a1-4f2d-9cba-1617a8c868c3/03e75c3c-24e7-4e68-a6f1-21728aaaa73e', 'name': 'vda'}]}} (__init__:355)</error>*

1 1

[JIRA] (OVIRT-2265) ovirt-engine cq failing on test 098_ovirt_provider_ovn.use_ovn_provider - libvirtError: 'queues' attribute must be positive number:
by Dafna Ron (oVirt JIRA) 28 Jun '18

28 Jun '18

Dafna Ron created OVIRT-2265: -------------------------------- Summary: ovirt-engine cq failing on test 098_ovirt_provider_ovn.use_ovn_provider - libvirtError: 'queues' attribute must be positive number: Key: OVIRT-2265 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2265 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest The change reported as responsible for the failure was a package change patch but I can see that some patches merged by Alona are more related to the issue. mail sent to list. Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/92567/ - packaging: Add python-netaddr requirement I actually think from the error its because of changes made to multiqueues https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to consider vmBase.multiQueuesEnabled attribute https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for calculating how many queues asign per vnic https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to VmBase https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues Enabled' to the relevant mappers https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues Enabled' to vm dialog Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 91784, 3 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 28 Jun '18

28 Jun '18

Change 91784,3 (ovirt-hosted-engine-ha) 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/91784/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8398/

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by Piotr Kliczewski (oVirt JIRA) 28 Jun '18

28 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Piotr Kliczewski commented on OVIRT-2259: ----------------------------------------- This could be related to jdk [bug|https://bugs.openjdk.java.net/browse/JDK-8182580] > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage
by Dafna Ron (oVirt JIRA) 28 Jun '18

28 Jun '18

Dafna Ron created OVIRT-2264: -------------------------------- Summary: Cannot deactivate Storage while there are running tasks on this Storage Key: OVIRT-2264 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2264 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we failed test: 007_sd_reattach.deactivate_storage_domain in vdsm project with error: Cannot deactivate Storage while there are running tasks on this Storage. -Please wait until tasks will finish and try again.]". HTTP response code is 409. I am opening this as a race in case something changed in OST tests which would cause this to repeat. https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2506 https://gerrit.ovirt.org/#/c/92313/2 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2
by Daniel Belenky (oVirt JIRA) 28 Jun '18

28 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2175: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Move oVirt projects to STDCI V2 > ------------------------------- > > Key: OVIRT-2175 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2175 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As STDCI V2 is live and production for a while now, it's time to proactively push and assist oVirt projects to move to STDCI V2. Projects will benefit from new STDCI V2 features such as the ability to modify the distributions and architectures they build on without having to send patches to the 'Jenkins' repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

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

28 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92319,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 92567,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/92319/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92567/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8394/

1 0

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

28 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92318,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 92567,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/92318/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92567/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8390/

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 283 - Failure!
by jenkins＠jenkins.phx.ovirt.org 28 Jun '18

28 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 283 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #283 [Gal Ben Haim] Make sure that crond is installed and running [Barak Korren] Install JJB via PIP instead of YUM [Barak Korren] Clean deprecation warning from JJB output [Barak Korren] Upgrade JJB to 1.6.2 ----------------- Failed Tests: ----------------- All tests passed

1 1

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

28 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92587,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 92567,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/92587/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92567/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8385/

1 0

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

28 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92149,13 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92567,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 92567,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/92149/13 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92567/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8380/

1 0

[JIRA] (OVIRT-2263) add uxd to oVirt github developers group
by Greg Sheremeta (oVirt JIRA) 27 Jun '18

27 Jun '18

Greg Sheremeta created OVIRT-2263: ------------------------------------- Summary: add uxd to oVirt github developers group Key: OVIRT-2263 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2263 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Hi, How can I add people to the oVirt github developers group? https://github.com/orgs/oVirt/teams/developers need to add our designers: https://github.com/lizsurette https://github.com/jennyhaines Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 92567,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 27 Jun '18

27 Jun '18

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

1 0

[CQ]: 92313,2 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 27 Jun '18

27 Jun '18

Change 92313,2 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92313/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2506/

1 0

[JIRA] (OVIRT-2255) build aborted on time out
by Gal Ben Haim (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2255?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2255: ------------------------------------- # attach_vm_network_to_host_0_static_config: Success (in 1:08:46) The test above took ~1 hour, [~lgoldber] [~ehaas(a)redhat.com] can you please take a look? > build aborted on time out > -------------------------- > > Key: OVIRT-2255 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2255 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_lago > > We had a test aborted which seemed to have been on time out. > Build was aborted: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8350/ > I can see it was a timeout: Timeout has been exceeded > sigterm was sent by lago: > '+ logger.success 'Cleanup done' > + logger.log SUCCESS 'Cleanup done' > + set +x > run_suite.sh::env_cleanup::SUCCESS:: Cleanup done > + exit 0 > + exit > Sending interrupt signal to process > sh: line 1: 47038 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/script.sh' > '/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests(a)tmp/durable-c13ed13b/jenkins-log.txt' 2>&1 > After 10s process did not stop' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Gal Ben Haim (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2231: -------------------------------- Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) > QEMU can't access "/home/jenkins/*" on FC28 slaves. > --------------------------------------------------- > > Key: OVIRT-2231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2231 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > Priority: Highest > > Lago creates VM images under "/home/jenkins", QEMU process fails to access those images because of missing permissions. > The solution is to set the "execute/search" bit on "/home/jenkins". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

oVirt infra weekly meeting notes 27.06.2018
by Evgheni Dereveanchin 27 Jun '18

27 Jun '18

Hi everyone, Please find the topics of this week's infra meeting below: *PHX - Jenkins- Security advisory out for several plugins OVIRT-2262 <https://ovirt-jira.atlassian.net/browse/OVIRT-2262>- Headers need to be added before next restart OVIRT-2199 <https://ovirt-jira.atlassian.net/browse/OVIRT-2199>- Parametrized remote trigger Plugin install requested OVIRT-2256 <https://ovirt-jira.atlassian.net/browse/OVIRT-2256>- New PHX subnet proposed by IT Other topics - Monitoring migration <http://8.43.85.199/nagios/> to OSAS in progress OVIRT-502 <https://ovirt-jira.atlassian.net/browse/OVIRT-502>- graphs need to be fixed- notifications must be verified- Jira redirect must be copied- RAM/CPU bumped on mailing lists server- Spamassassin issue with slow scanningAction Items - Improve monitoring of the lists server- Ansible user management- Document OSAS jump host (allowed user keys here <https://gitlab.com/osas/community-cage-infra-ansible/blob/master/group_vars…>)- Update oVirt infra users here <https://gerrit.ovirt.org/gitweb?p=infra-ansible.git;a=tree;f=roles/admin_ss…> + roles/admin_ssh_keys/tasks/main.yml- Open ticket to discuss ansible-pull <https://docs.ansible.com/ansible/2.4/ansible-pull.html>* -- Regards, Evgheni Dereveanchin

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by danken (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] danken commented on OVIRT-2259: ------------------------------- I don't really understand the problem, nice [~nsoffer(a)redhat.com] reports that Engine running on el7 *is* able to ssh into fc28 host. If you can hack ssh config on Engine side, it would be great. If hacking on the host is needed, it is less great, but it is still better to hack it, file a bug, and get on with OST. > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2181) Release lago-ovirt for fc28
by Eyal Edri (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2181?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2181: ----------------------------- Assignee: Gal Ben Haim (was: infra) Status: In Progress (was: To Do) Looks like work started as I see unstable release ready: https://resources.ovirt.org/repos/lago/unstable/0.0/latest/rpm/fc28/noarch/… So pending an official release. > Release lago-ovirt for fc28 > --------------------------- > > Key: OVIRT-2181 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2181 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: Gal Ben Haim > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2256) Install the Parametrized Remote Trigger plugin
by Evgheni Dereveanchin (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2256?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2256: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Install the Parametrized Remote Trigger plugin > ---------------------------------------------- > > Key: OVIRT-2256 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2256 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Please install the [Parametrized Remote Trigger|https://plugins.jenkins.io/Parameterized-Remote-Trigger] plugin so we can use it to trigger jobs in remote Jenkins instances. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 92553, 1 (ovirt-appliance) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jun '18

27 Jun '18

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

2 1

[JIRA] (OVIRT-2262) Apply fixes for Jenkins Security Advisory 2018-06-25
by Evgheni Dereveanchin (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2262?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2262: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Apply fixes for Jenkins Security Advisory 2018-06-25 > ---------------------------------------------------- > > Key: OVIRT-2262 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2262 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > There's a new security advisory out fixing security issues in plugins we use: > https://jenkins.io/security/advisory/2018-06-25/ > We need to apply it to our Jenkins -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2262) Apply fixes for Jenkins Security Advisory 2018-06-25
by Evgheni Dereveanchin (oVirt JIRA) 27 Jun '18

27 Jun '18

Evgheni Dereveanchin created OVIRT-2262: ------------------------------------------- Summary: Apply fixes for Jenkins Security Advisory 2018-06-25 Key: OVIRT-2262 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2262 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra There's a new security advisory out fixing security issues in plugins we use: https://jenkins.io/security/advisory/2018-06-25/ We need to apply it to our Jenkins -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by Martin Perina (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Martin Perina commented on OVIRT-2259: -------------------------------------- The only thing that came to my mind is to enable the same SSH ciphers/algorithms on FC28 which are enabled on EL7 now On Wed, 27 Jun 2018, 11:24 Gal Ben Haim (oVirt JIRA), < > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by Gal Ben Haim (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2259: ------------------------------------- [~mwperina] Is there any temporary workaround for this issue? I really want to go forward and discover other issues that are related to FC28. > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by sbonazzo (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-2259: ---------------------------- External issue ID: https://bugzilla.redhat.com/show_bug.cgi?id=1591801 Status: Blocked (was: To Do) > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by sbonazzo (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2259: --------------------------------- For reference, bugzilla is https://bugzilla.redhat.com/show_bug.cgi?id=1591801 > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 515 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '18

27 Jun '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/515/ Build Number: 515 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #515 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- No tests ran.

1 3

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

27 Jun '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/71/ Build Number: 71 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #71 [Marcin Mirecki] network: Workaround for missing shade MTU functionality [Evgheni Dereveanchin] load OVS module from global_setup [Sandro Bonazzola] ovirt-engine-sdk: drop ppc64le on fedora ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 320 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '18

27 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/… Build Number: 320 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #320 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- All tests passed

1 2

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 391 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '18

27 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-mast… Build Number: 391 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #391 [Marcin Mirecki] network: Workaround for missing shade MTU functionality [Evgheni Dereveanchin] load OVS module from global_setup ----------------- Failed Tests: ----------------- All tests passed

1 1

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by Martin Perina (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Martin Perina commented on OVIRT-2259: -------------------------------------- We already have a bug for that issue, we need to upgrade apache ssh java library from 0.12 to 1.y, which is a huge API change. Btw we have already tried that upgrade and we failed, so it is not something we will be able to fix in a few days, but we will put a priority on that in upcoming weeks. Martin On Tue, 26 Jun 2018, 16:40 Gal Ben Haim (oVirt JIRA), < > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0