After an upgrade of your hosts, you will need to reboot your host. In this article, we will take you through the process of doing that.
- vCenter Environment
Rebooting the Host
Log into your vCenter environment. We will first put the host we are rebooting into maintenance mode. To do so, right-click the host in question and select Maintenance Mode and then Enter Maintenance Mode.
Click OK on the ensuing pop-up and leave the box next to "Move powered-off and suspended virtual machines to other hosts in the cluster" checked. Your VMs on the host in maintenance mode will be moved to another active host.
Verify that all VMs have been moved off of the host by selecting the VM tab on the host in question. If VMs are still present, refer to the Troubleshooting section of this article.
Once the host is in Maintenance Mode, right-click on the host and select Power and then Reboot from the drop-down menu.
You will be prompted to enter a reason for the host reboot. Enter the reason and click OK.
Please allow 10-15 minutes for the operation to complete. Once the host comes back online, right-click the host again and select Maintenance Mode and Exit Maintenance Mode from the drop-down menu.
Verify that the correct version is showing on the host.
Not enough resources on additional host(s) to facilitate migration
Verify that the other hosts in your cluster are not at their capacity limits. You can check this on the Summary tab for the host in the top-right corner.
If all other hosts are full or close to full, you can contact OVHcloud support to have a spare host provided for you during the upgrade period.
Affinity rules are in place
Click the cluster containing the host in maintenance mode and navigate to the Configure tab for the cluster. Under "Configuration", select "VM/Host Rules". If affinity rules are in place, you will see them in the list below.
Highlight a rule and click the Edit button. Uncheck the "Enable rule" box to disable the rule. You will need to do this for each rule that exists in your environment.
The automation should now be able to proceed. You will need to remember to re-enable your affinity rules after the upgrade is complete.
Attached devices/ISOs on VM(s)
If you receive an error similar to the one below, this could be the result of an ISO or a separate device such as the HD Audio device listed below. This will need to be removed from from the VM(s) in order for the migration to continue.
Click on the VM that has the attached device. Click Actions and then Edit Settings.
If an ISO is mounted, either change the CD/Drive mount to client device or uncheck the "Connected" checkbox. Please note that this will need to be done for each VM with a mounted ISO.
If the migration task is still stuck after verifying these steps, vMotion will need to take place manually.
Navigate to the host in maintenance mode and select the VMs tab. Select your VM(s), right-click on the highlighted VM(s) and navigate to Migrate. Please note that multiple VMs can be selected by either pressing Shift + Right Mouse Button or Ctrl + Right Mouse Button.
- Shift + Right Mouse Button will grab all VMs between your top most selected and your bottom most selected or visa versa.
- Ctrl + Right Mouse Button will add individual VMs to your highlighted list.
Proceed through the migration menu. Verify that "change compute resource only" is selected and click Next.
Select the host that to which you would like to migrate the VMs and click Next. Resources will need to be available on your additional host in order for the migration to proceed.
Finally, select the correct network for your VMs and click Next. Once the migration is complete, you are ready to reboot.
Having read this article, you should be able to reboot your host after an upgrade as well as perform basic troubleshooting steps for the operation.