[ovirt-users] Re: Unable to import engine

On Sun, Nov 18, 2018 at 8:53 AM Alex K <rightkicktech(a)gmail.com&gt; wrote: > > > On Sat, Nov 17, 2018, 19:32 Gianluca Cecchi <gianluca.cecchi(a)gmail.com&gt; > wrote: > >> >> >> Il giorno Sab 17 Nov 2018 14:07 Alex K <rightkicktech(a)gmail.com&gt; ha >> scritto: >> >>> Hi all, >>> >>> I had a setup with ovirt 4.2.0 which at some point the engine stopped >>> responding, due to some split brain issues. >>> >>> Since was not able to resolve the split brain, I proceeded to redeploy >>> the engine. >>> >>> The steps I followed: >>> 1. upgrade servers (yum update) >>> 2. ran ovirt-hosted-engine-cleanup >>> 3. deployed engine (now 4.2.7) >>> >>> The deploy was successful and was able to add a new data domain. >>> The issue is that at this point I would expect the engine storage >>> domain and VM to be automatically imported, but it is not. At HA agent logs >>> at the server I see: >>> >>> MainThread::INFO::2018-11-17 >>> 12:55:51,856::states::444::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) >>> Engine vm running on localhost >>> MainThread::WARNING::2018-11-17 >>> 12:55:52,145::ovf_store::140::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) >>> Unable to find OVF_STORE >>> MainThread::ERROR::2018-11-17 >>> 12:55:52,146::config_ovf::84::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config.vm::(_get_vm_conf_content_from_ovf_store) >>> Unable to identify the OVF_STORE volume, falling back to initial vm.conf. >>> Please ensure you already added your first data domain for regular VMs >>> MainThread::INFO::2018-11-17 >>> 12:55:52,246::hosted_engine::491::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) >>> Current state EngineUp (score: 3400) >>> >>> While at engine.log of engine VM I see: >>> >>> 2018-11-17 12:47:14,748Z INFO >>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] >>> (EE-ManagedThreadFactory-engineScheduled-Thread-51) [] VM >>> '88dacb07-45f1-4bc1-80a0-9434d530eaaa' was discovered as 'Up' on VDS >>> '6eff2018-516d-4af1-807d-ecc31d024f4d'(v0.maya) >>> 2018-11-17 12:47:14,773Z INFO >>> [org.ovirt.engine.core.bll.AddUnmanagedVmsCommand] >>> (EE-ManagedThreadFactory-engineScheduled-Thread-51) [51c593c1] Running >>> command: AddUnmanagedVmsCommand internal: true. >>> 2018-11-17 12:47:14,775Z INFO >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] >>> (EE-ManagedThreadFactory-engineScheduled-Thread-51) [51c593c1] START, >>> DumpXmlsVDSCommand(HostName = v0.maya, >>> Params:{hostId='6eff2018-516d-4af1-807d-ecc31d024f4d', >>> vmIds='[88dacb07-45f1-4bc1-80a0-9434d530eaaa]'}), log id: 44bb4e0a >>> 2018-11-17 12:47:14,779Z INFO >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DumpXmlsVDSCommand] >>> (EE-ManagedThreadFactory-engineScheduled-Thread-51) [51c593c1] FINISH, >>> DumpXmlsVDSCommand, return: {88dacb07-45f1-4bc1-80a0-9434d530eaaa=<domain >>> type='kvm' id='7'> >>> ... >>> <some kind of XML> >>> ... >>> 2018-11-17 12:47:14,793Z WARN >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] >>> (EE-ManagedThreadFactory-engineScheduled-Thread-51) [51c593c1] null >>> architecture type, replacing with x86_64, VM [HostedEngine] >>> >>> Sth is causing engine not not getting imported. >>> Tried to run hosted-engine –reinitialize-lockspace, since I was getting >>> some lockspace errors, but no change. >>> >>> Any idea what could be causing this? >>> I am left with little time due to the site being production. Any idea >>> is appreciated. >>> >>> Thanx, >>> Alex >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/M4DXHOUQ45Q... >> >> >> In step 3 how did you deploy engine? >> I had the same problem some days ago and was due to a bug in using >> command line and excluding ansible (option --no-ansible) >> I solved redeploying using the default that is with ansible >> > I deployed with --no-ansible flag since the ansible way was giving me an > error (sth with localhost). I can try ansible to check what was the error. > The error I am getting when trying to deploy with ansible is the following: 2018-11-17 09:03:50,378+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 hostname_resolution_output: {'stderr_lines': [], u'changed': True, u'end': u'2018-11-17 09:03:48.572863', u'stdout': u'', u'cmd': u'getent ahostsv4 v0.maya | grep v0.maya', u'failed': True, u'delta': u'0:00:00.005712', u'stderr': u'', u'rc': 1, u'msg': u'non-zero return code', 'stdout_lines': [], u'start': u'2018-11-17 09:03:48.567151'} 2018-11-17 09:03:51,280+0000 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:100 TASK [Check address resolution] 2018-11-17 09:03:52,082+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 {u'msg': u'Unable to resolve address\n', u'changed': False, u'_ansible_no_log': False} 2018-11-17 09:03:52,182+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:98 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Unable to resolve address\n"} 2018-11-17 09:03:52,784+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:94 PLAY RECAP [localhost] : ok: 16 changed: 3 unreachable: 0 skipped: 4 failed: 1 2018-11-17 09:03:52,884+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:180 ansible-playbook rc: 2 2018-11-17 09:03:52,884+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils.run:187 ansible-playbook stdout: -- File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/ansible_utils.py", line 194, in run raise RuntimeError(_('Failed executing ansible-playbook')) RuntimeError: Failed executing ansible-playbook 2018-11-17 09:03:52,886+0000 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Closing up': Failed executing ansible-playbook 2018-11-17 09:03:52,887+0000 DEBUG otopi.context context.dumpEnvironment:859 ENVIRONMENT DUMP - BEGIN 2018-11-17 09:03:52,887+0000 DEBUG otopi.context context.dumpEnvironment:869 ENV BASE/error=bool:'True' 2018-11-17 09:03:52,887+0000 DEBUG otopi.context context.dumpEnvironment:869 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError('Failed executing ansible-playbook',), <traceback object at 0x7fefb0248f38>)]' How Can I overcome this? I recall I've seen this on past attempts also and was able to proceed only with the traditional python (--no-ansible) way.

> HIH, >> Gianluca >> >