Re: [ovirt-users] InClusterUpgrade Scheduling Policy

Hi Scott, On Thu, Jun 23, 2016 at 8:54 PM, Scott <romracer(a)gmail.com&gt; wrote: That is correct, only the he-agents on each host decide where the hosted engine VM can start Also true, it is very limited what you can currently do with the hosted engine VM. That is indeed something the InClusterUpgrade does not take into consideration. I will file a bug report. But what you can do is the following: You can create a temporary cluster, move one host and the hosted engine VM there, upgrade all hosts and then start the hosted-engine VM in the original cluster again. The detailed steps are: 1) Enter the global maintenance mode 2) Create a temporary cluster 3) Put one of the hosted engine hosts which does not currently host the engine into maintenance 4) Move this host to the temporary cluster 5) Stop the hosted-engine-vm with `hosted-engine --destroy-vm` (it should not come up again since you are in maintenance mode) 6) Start the hosted-egine-vm with `hosted-engine --start-vm` on the host in the temporary cluster 7) Now you can enable the InClusterUpgrade policy on your main cluster 7) Proceed with your main cluster like described in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtuali... 8) When all hosts are upgraded and InClusterUpgrade policy is disabled again, move the hosted-engine-vm back to the original cluster 9) Upgrade the last host 10) Migrate the last host back 11) Delete the temporary cluster 12) Deactivate maintenance mode Adding Sandro and Roy to keep me honest. Roman