<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 1, 2017 at 3:19 PM, Chris Adams <span dir="ltr"><<a href="mailto:cma@cmadams.net" target="_blank">cma@cmadams.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">Once upon a time, Simone Tiraboschi <<a href="mailto:stirabos@redhat.com">stirabos@redhat.com</a>> said:<br>
</span><span class="gmail-">> > I recreated a 3.5 setup and upgraded the engine to 3.6 - that should<br>
> > have been enough to import the hosted engine storage domain, right?<br>
><br>
> Did you also raised the cluster compatibility level to 3.6 on the engine?<br>
<br>
</span>No (I didn't realize this didn't happen until that was changed).<br>
<br>
However, now I'm back into the catch-22 of 3.6.7+hosted engine: the<br>
cluster compatibility level can't be raised while there's a running VM,<br>
and that includes the hosted engine.<br></blockquote><div><br></div><div>Please see this one:</div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1364557">https://bugzilla.redhat.com/show_bug.cgi?id=1364557</a><br></div><div><br></div><div>Simply <span style="color:rgb(0,0,0);white-space:pre-wrap">define 'InClusterUpgrade' scheduling policy on the HE VM cluster</span></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail-HOEnZb"><div class="gmail-h5">--<br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div></div>