<div dir="ltr"><div>Hi,<br></div><div><br></div><div>I was able to remove the hostedEngine VM, but I didn't succeed to remove the old hostedEngine Storage domain.</div><div>I tried several time to remove it, but I couldn't, the VM engine goes in pause mode. All I could do is to detach the hostedEngine from the datacenter. I then put all the other data domains in maintenance mode, the I reactivated my master data domain hoping that it will import the new hostedEngine domain, but without luck.</div><div><br></div><div>It seems like there is something missing in this procedure.<br></div><div><br></div>Regards<br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-08-25 9:28 GMT+01:00 Alan Griffiths <span dir="ltr"><<a href="mailto:apgriffiths79@gmail.com" target="_blank">apgriffiths79@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>As I recall (a few weeks ago now) it was after restore, once the host had been registered in the Manager. However, I was testing on 4.0, so maybe the behaviour is slightly different in 4.1.<br><br></div>Can you see anything in the Engine or vdsm logs as to why it won't remove the storage? Perhaps try removing the stale HostedEngine VM ?<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 25 August 2017 at 09:14, wodel youchi <span dir="ltr"><<a href="mailto:wodel.youchi@gmail.com" target="_blank">wodel.youchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi and thanks,<div dir="auto"><br></div><div dir="auto">But when to remove the hosted_engine storage ? During the restore procedure or after ? Because after I couldn't do it, the manager refused to put that storage in maintenance mode.</div><div dir="auto"><br></div><div dir="auto">Regards</div></div><div class="m_4457919776337353415HOEnZb"><div class="m_4457919776337353415h5"><div class="gmail_extra"><br><div class="gmail_quote">Le 25 août 2017 08:49, "Alan Griffiths" <<a href="mailto:apgriffiths79@gmail.com" target="_blank">apgriffiths79@gmail.com</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">As I recall from my testing. If you remove the old hosted_storage domain then the new one should get automatically imported.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 24 August 2017 at 23:03, wodel youchi <span dir="ltr"><<a href="mailto:wodel.youchi@gmail.com" target="_blank">wodel.youchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>I am testing the backup and restore procedure of the Self-hosted Engine, and I have a problem.</div><div><br></div><div>This haw I did the test.</div><div><br></div><div>I have two hypervisors hosted-engine. I am used iSCSI disk for the VM engine.</div><div><br></div><div>I followed the procedure described in the Self-hosted Engine document to execute the backup, I put the first host in maintenance mode, the I create the backup and save it elsewhere.</div><div><br></div><div>Then I've create a new iscsi disk, I reinstalled the first host with the save IP/hostname, then I followed the restore procedure to get the Manager up and running again.</div><div>- hosted-engine --deploy</div><div>- do not execute engine-setup, restore backup first</div><div>- execute engine-setup</div><div>- remove the host from the manager<br></div><div>- synchronize the restored manger with the host</div><div>- finalize deployment.</div><div><br></div><div>all went well till this point, but I have a problem with the VM-engine, it is shown as down in the admin portal. the ovirt-ha-agent cannot retrieve the VM config from the shared storage.</div><div><br></div><div>I think the problem, is that the hosted-engine storage domain is still pointing to the old disk of the old manager and not the new one. I don't know where is this information is stored, in the DB or in the Manager's config files, but when I click Manager hosted-engine domain, I can see the old LUN grayed and the new one (which is used by the restored Manager) is not grayed.</div><div><br></div><div>How can I fix this?<br></div><div><br></div><div></div><div></div><div>Regards.<br></div></div><div id="m_4457919776337353415m_9177001278217562974m_7731007781891096843m_3883279741882476845DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br> <table style="border-top:1px solid #d3d4de">
<tbody><tr>
<td style="width:55px;padding-top:18px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" style="width:46px;height:29px" width="46" height="29"></a></td>
<td style="width:470px;padding-top:17px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Garanti sans virus. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" style="color:#4453ea" target="_blank">www.avast.com</a> </td>
</tr>
</tbody></table>
<a href="#m_4457919776337353415_m_9177001278217562974_m_7731007781891096843_m_3883279741882476845_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></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></div><br></div>
</blockquote></div></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>