[ovirt-users] Re: Unable to import engine

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.

HIH, > Gianluca >