Re: [ovirt-users] hosted-engine deploy error terminal state

On Tue, Aug 16, 2016 at 5:34 PM, Maxence Sartiaux <contact(a)makz.me&gt; wrote: Please provide more details about what you are trying to do. It seems like you already have an engine. Can't tell if it's a hosted engine or not. Is it? It seems like the host you are trying to deploy is/was already managed by your engine. Is it? Generally speaking, we do not allow "converting" an engine to a hosted engine nor doing 'hosted-engine --deploy' on a host already managed by the/an engine. For the former, please check [1]. For the latter, you should first remove the host from the engine. [1] is very old, and some details are different today, but the principles remain. I recommend trying this first on an isolated test env before doing on production. BTW, the above does not explain your failure. Your specific failure is: 2016-08-16 15:22:10 INFO otopi.plugins.gr_he_setup.engine.add_host engineapi.get_engine_api:51 Connecting to the Engine 2016-08-16 15:22:10 DEBUG otopi.plugins.gr_he_setup.engine.add_host add_host._closeup:513 Getting the list of available clusters via engine's APIs 2016-08-16 15:37:10 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/gr-he-setup/engine/add_host.py", line 554, in _closeup net_info = CachingNetInfo(vds_info.capabilities(conn)) File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vds_info.py", line 31, in capabilities result = conn.getVdsCapabilities() File "/usr/lib/python2.7/site-packages/vdsm/jsonrpcvdscli.py", line 153, in _callMethod raise JsonRpcNoResponseError(method) JsonRpcNoResponseError: [-32605] No response for JSON-RPC Host.getCapabilities request. To me it seems like 'hosted-engine --deploy' managed to connect to the engine (not sure which, existing or one created in new hosted-engine vm) but fails to get the list of clusters, probably because the engine fails to connect to one or more hosts. Can't see that in the attached engine.log btw - either it's from the wrong machine, or wrong time/timezone, something like that. [1] http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-eng... Best, -- Didi