<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 21, 2017 at 3:06 PM, Devin A. Bougie <span dir="ltr"><<a href="mailto:devin.bougie@cornell.edu" target="_blank">devin.bougie@cornell.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mar 20, 2017, at 12:54 PM, Simone Tiraboschi <<a href="mailto:stirabos@redhat.com">stirabos@redhat.com</a>> wrote:<br>
> The engine should import it by itself once you add your first storage domain for regular VMs.<br>
> No manual import actions are required.<br>
<br>
</span>It didn't seem to for us. I don't see it in the Storage tab (maybe I shouldn't?). I can install a new host from the engine web ui, but I don't see any hosted-engine options. If I put the new host in maintenance and reinstall, I can select DEPLOY under "Choose hosted engine deployment action." However, the web UI than complains that:<br>
Cannot edit Host. You are using an unmanaged hosted engine VM. P{ease upgrade the cluster level to 3.6 and wait for the hosted engine storage domain to be properly imported.<br>
<br></blockquote><div><br></div><div>Did you already add your first storage domain for regular VMs?</div><div>If also that one is on iSCSI, it should be connected trough a different iSCSI portal.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is on a new 4.1 cluster with the hosted-engine created using hosted-engine --deploy on the first host.<br>
<span class=""><br>
> No, a separate network for the storage is even recommended.<br>
<br>
</span>Glad to hear, thanks!<br>
<span class="HOEnZb"><font color="#888888"><br>
Devin<br>
<br>
</font></span></blockquote></div><br></div></div>