<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 21, 2017 at 5:20 AM, Andrew Dent <span dir="ltr"><<a href="mailto:adent@ctcroydon.com.au" target="_blank">adent@ctcroydon.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u><div><div>Hi Yaniv</div><div><br></div><div>I found a solution. </div><div>Our Ovirt 3.6 AIO box was still running and had those VMs still configured in their pre exported and switch off state. </div><div>I removed any snap shots I found from those pre exported VMs, then copied the disk image files and other bits from h<span style="font-size:12pt">ost01 (Ovirt v 4.1) back into the Ovirt 3.6 AIO box, and were needed fixing the relevent IDs to be what the Engine in the Ovirt 3.6 box expected. </span></div><div><span style="font-size:12pt">The VMs then started up properly again without hassle and with the latest files on the Ovirt 3.6 AIO box. </span></div></div></blockquote><div><br></div><div>Well done and kudos for the resourcefulness!</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br></div><div><span style="font-size:12pt">So now in the progress of rebuilding host01 with </span><span style="font-size:12pt">hosted-engine </span><span style="font-size:12pt">v4.1 </span></div><div><br></div><div id="m_7537265340420555881signature_old"><div id="m_7537265340420555881xa78294227b5f49c">
<div class="m_7537265340420555881WordSection1">
<div id="m_7537265340420555881xb71224f920234978acc74f4d23143069"><div class="m_7537265340420555881WordSection1"><p class="MsoNormal"><font face="Tahoma"><font size="3" style="font-size:12pt">Kind r</font><span style="font-size:12pt">egards</span></font></p><p class="MsoNormal"><font size="3" style="font-size:12pt" face="Tahoma"><br></font></p><p class="MsoNormal"><font size="3" style="font-size:12pt" face="Tahoma">Andrew </font></p></div></div></div></div></div><span class="">
<div>------ Original Message ------</div>
<div>From: "Yaniv Kaul" <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></div>
<div>To: "Andrew Dent" <<a href="mailto:adent@ctcroydon.com.au" target="_blank">adent@ctcroydon.com.au</a>></div>
<div>Cc: "users" <<a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>></div>
<div>Sent: 18/06/2017 6:00:09 PM</div>
<div>Subject: Re: [ovirt-users] hosted-engine VM and services not working</div><div><br></div>
</span><div id="m_7537265340420555881xbea74d01f04742a"><blockquote cite="http://249bdf9e95f568dc618088083841b2b46780224d@localhost" type="cite" class="m_7537265340420555881cite2">
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Sat, Jun 17, 2017 at 12:50 AM, <span dir="ltr"><<a href="mailto:adent@ctcroydon.com.au" target="_blank">adent@ctcroydon.com.au</a>></span> wrote:<br></span><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>If I reinstall and the rerun the hosted-engine setup how do I get the VMs in their current running state back into and being recognised by the new hosted engine?<br></div></div></blockquote><div><br></div></span><span class=""><div>Current running state is again quite challenging. You'll need to fix the hosted-engine.</div><div><br></div><div>Can import the storage domain? (not for running VMs)</div><div>Y.</div><div><br></div></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><br>Kind regards<span class="m_7537265340420555881HOEnZb"><font color="#888888"><div><br></div><div>Andrew</div></font></span></div><div><div class="h5"><span><div><br>On 17 Jun 2017, at 6:54 AM, Yaniv Kaul <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>> wrote:<br><br></div></span><blockquote type="cite" class="m_7537265340420555881cite"><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, Jun 16, 2017 at 9:11 AM, Andrew Dent <span dir="ltr"><<a href="mailto:adent@ctcroydon.com.au" target="_blank">adent@ctcroydon.com.au</a>></span> wrote:<br></span><div><div class="m_7537265340420555881h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div><div>Hi</div><div><br></div><div>Well I've got myself into a fine mess. </div><div><br></div><div>host01 was setup with hosted-engine v4.1. <span style="font-size:12pt">This was successful. </span></div><div><span style="font-size:12pt">Imported 3 VMs from a v3.6 OVirt AIO instance. (This OVirt 3.6 is still running with more VMs on it)</span></div><div>Tried to add host02 to the new Ovirt 4.1 setup. This partially succeeded but I couldn't add any storage domains to it. Cannot remember why. </div><div>In Ovirt engine UI I removed host02. </div><div>I reinstalled host02 with Centos7, tried to add it and Ovirt UI told me it was already there (but it wasn't listed in the UI). </div><div>Renamed the reinstalled host02 to host03, changed the ipaddress, reconfig the DNS server and added host03 into the Ovirt Engine UI. </div><div>All good, and I was able to import more VMs to it. </div><div>I was also able to shutdown a VM on host01 assign it to host03 and start the VM. Cool, everything working. </div><div>The above was all last couple of weeks. </div><div><br></div><div>This week I performed some yum updates on the Engine VM. No reboot. </div><div>Today noticed that the Ovirt services in the Engine VM were in a endless restart loop. They would be up for a 5 minutes and then die. </div><div>Looking into /var/log/ovirt-engine/eng<wbr>ine.log and I could only see errors relating to host02. Ovirt was trying to find it and failing. Then falling over. </div><div>I ran "hosted-engine --clean-metadata" thinking it would cleanup and remove bad references to hosts, but now realise that was a really bad idea as it didn't do what I'd hoped. </div><div>At this point the sequence below worked, I could login to Ovirt UI but after 5 minutes the services would be off</div><div><div>
<span style="color:rgb(34,34,34);font-family:Verdana,Arial,Helvetica,sans-serif;font-variant-ligatures:normal;background-color:rgb(255,255,255)">service ovirt-engine restart</span></div></div><div><span style="color:rgb(34,34,34);font-family:Verdana,Arial,Helvetica,sans-serif;font-variant-ligatures:normal;background-color:rgb(255,255,255)"><div>
<span style="font-variant-ligatures:normal">service ovirt-websocket-proxy restart</span></div><div><span style="font-variant-ligatures:normal"><div>
<span style="font-variant-ligatures:normal">service httpd restart</span></div></span></div></span></div><div><br></div><div>I saw some reference to having to remove hosts from the database by hand in situations where under the hood of Ovirt a decommission host was still listed, but wasn't showing in the GUI. </div><div>So I removed reference to host02 (vds_id and host_id) in the following tables in this order. </div><div><span style="font-size:12pt">vds_dynamic</span></div><div><div id="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923x0ec1289986994fb5ac309827edd33abe">
<div><div><span style="font-size:12pt">vds_statistics</span></div><div><div id="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923x87d978c56880415e9594d7fe317f30f3">
<div><div><div id="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923x0ec1289986994fb5ac309827edd33abe"><div><div>vds_static</div><div></div></div></div></div></div></div></div><div></div></div></div></div><div>host_device</div><div><br></div><div>Now when I try to start ovirt-websocket it will not start</div><div>service ovirt-websocket start<br>Redirecting to /bin/systemctl start ovirt-websocket.service<br>Failed to start ovirt-websocket.service: Unit not found.</div><div><br></div><div>I'm now thinking that I need to do the following in the engine VM</div><div><div>
<pre class="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923highlight m_7537265340420555881m_-8696545545904220606m_-2002812221470261923plaintext"><code># engine-cleanup
# yum remove ovirt-engine
# yum install ovirt-engine
# engine-setup </code></pre></div></div><div>But to run engine-cleanup I need to put the engine-vm into maintenance mode and because of the --clean-metadata that I ran earlier on host01 I cannot do that. </div><div><br></div><div>What is the best course of action from here?</div></div></blockquote><div><br></div></div></div><span><div>To be honest, with all the steps taken above, I'd install everything (including OS) from scratch...</div><div>There's a bit too much mess to try to clean up properly here.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br></div><div id="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923signature_old"><div id="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923xbaf36d997b7f497">
<div class="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923WordSection1">
<div id="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923xb71224f920234978acc74f4d23143069"><div class="m_7537265340420555881m_-8696545545904220606m_-2002812221470261923WordSection1"><p class="MsoNormal"><font face="Tahoma"><span style="font-size:16px">Cheers</span></font></p><span class="m_7537265340420555881m_-8696545545904220606HOEnZb"><font color="#888888"><p class="MsoNormal"><br></p><p class="MsoNormal"><font face="Tahoma"><span style="font-size:16px">Andrew</span></font></p></font></span></div></div></div></div></div>
</div><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></span></div><br></div></div>
</div></blockquote></div></div></div></blockquote></div><br></div></div>
</blockquote></div>
</div></blockquote></div><br></div></div>