<div dir="ltr">Hi Roman,<div><br></div><div>Thanks for the detailed steps. I follow the idea you have outlined and I think its easier than what I thought of (moving my self hosted engine back to physical hardware, upgrading and moving it back to self hosted). I will give it a spin in my build RHEV cluster tomorrow and let you know how I get on.</div><div><br></div><div>Thanks again,</div><div>Scott</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 23, 2016 at 2:41 PM Roman Mohr <<a href="mailto:rmohr@redhat.com">rmohr@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Scott,<br>
<br>
On Thu, Jun 23, 2016 at 8:54 PM, Scott <<a href="mailto:romracer@gmail.com" target="_blank">romracer@gmail.com</a>> wrote:<br>
> Hello list,<br>
><br>
> I'm trying to upgrade a self-hosted engine RHEV environment running 3.5/el6<br>
> to 3.6/el7. I'm following the process outlined in these two documents:<br>
><br>
> <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Self-Hosted_Engine_Guide/Upgrading_the_Self-Hosted_Engine_from_6_to_7.html" rel="noreferrer" target="_blank">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Self-Hosted_Engine_Guide/Upgrading_the_Self-Hosted_Engine_from_6_to_7.html</a><br>
> <a href="https://access.redhat.com/solutions/2300331" rel="noreferrer" target="_blank">https://access.redhat.com/solutions/2300331</a><br>
><br>
> The problem I'm having is I don't seem to be able to apply the<br>
> "InClusterUpgrade" policy (procedure 5.5, step 4). I get the following<br>
> error:<br>
><br>
> Can not start cluster upgrade mode, see below for details:<br>
> VM HostedEngine with id 5ca9cb38-82e5-4eea-8ff6-e2bc33598211 is configured<br>
> to be not migratable.<br>
><br>
That is correct, only the he-agents on each host decide where the<br>
hosted engine VM can start<br>
<br>
> But the HostedEngine VM is not one I can edit due to being mid-upgrade. And<br>
> even if I could, the setting its complaining about can't be managed by the<br>
> engine (I tried in another RHEV instance).<br>
><br>
Also true, it is very limited what you can currently do with the<br>
hosted engine VM.<br>
<br>
<br>
> Is this a bug? What am I missing to be able to move on? As it seems now,<br>
> the InClusterUpgrade scheduling policy is useless and can't actually be<br>
> used.<br>
<br>
That is indeed something the InClusterUpgrade does not take into<br>
consideration. I will file a bug report.<br>
<br>
But what you can do is the following:<br>
<br>
You can create a temporary cluster, move one host and the hosted<br>
engine VM there, upgrade all hosts and then start the hosted-engine VM<br>
in the original cluster again.<br>
<br>
The detailed steps are:<br>
<br>
1) Enter the global maintenance mode<br>
2) Create a temporary cluster<br>
3) Put one of the hosted engine hosts which does not currently host<br>
the engine into maintenance<br>
4) Move this host to the temporary cluster<br>
5) Stop the hosted-engine-vm with `hosted-engine --destroy-vm` (it<br>
should not come up again since you are in maintenance mode)<br>
6) Start the hosted-egine-vm with `hosted-engine --start-vm` on the<br>
host in the temporary cluster<br>
7) Now you can enable the InClusterUpgrade policy on your main cluster<br>
7) Proceed with your main cluster like described in<br>
<a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Self-Hosted_Engine_Guide/Upgrading_the_Self-Hosted_Engine_from_6_to_7.html" rel="noreferrer" target="_blank">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Self-Hosted_Engine_Guide/Upgrading_the_Self-Hosted_Engine_from_6_to_7.html</a><br>
8) When all hosts are upgraded and InClusterUpgrade policy is disabled<br>
again, move the hosted-engine-vm back to the original cluster<br>
9) Upgrade the last host<br>
10) Migrate the last host back<br>
11) Delete the temporary cluster<br>
12) Deactivate maintenance mode<br>
<br>
Adding Sandro and Roy to keep me honest.<br>
<br>
Roman<br>
<br>
><br>
> Thanks for any suggestions/help,<br>
> Scott<br>
><br>
> _______________________________________________<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/listinfo/users</a><br>
><br>
</blockquote></div>