The following article will walk you through the upgrade requirements you will need to complete based on the current phase of the automated vCenter v6.7u3f build'15976728' upgrade project.
Please check your email for all OVHcloud communications relating to this project.
Phase IV - vCenter Major Upgrade - CURRENT PHASE
The final phase of our vCenter Major Upgrade does not contain any per-requisites to the upgrade maintenance window. However, upon completion of our upgrade automation, each host will have a 7-day period where a host reboot is required.
Please see the steps below on how to reboot your host(s) before the end of the 7-day period. After which, we will complete the host reboot on your behalf for any host that has not been rebooted.
- Put the host that requires a reboot into maintenance mode. This is done by right clicking on the desired host and selecting maintenance mode. The VMs will be automatically migrated to other hosts within your environment, once this task kicks off.
- You will be prompted to verify that you would like to proceed. Please make sure that the checkbox labeled "Move powered-off and suspended virtual machines to other hosts in the cluster" is checked. This should be checked by default.
- Verify that all VMs have migrated from the host by selecting the "VM" tab located on that specific host. If VMs are still present, please see the troubleshooting steps at the end of this KB.
- Once the host is in Maintenance Mode, right click on the host that you have placed into maintenance mode and select "Reboot".
- You will be prompted to enter a reason for the host reboot.
- Allow 10-15 min for the host to finish the reboot.
- Once the host has come back online in vCenter, right click the host again and exit maintenance mode.
- Verify that the correct version is showing on the host. The version should show 6.7.
Troubleshooting Scenarios if VM's did not migrate after placing your host in maintenance mode:
Not enough resources on additional host(s) to facilitate migration
Verify that the other host within your Cluster are not at there capacity limit by clicking on an individual host and selecting the summary tab.
In the top right corner of your browser you will see the resources used and available on your host. Please note that you will need to verify all of your hosts to rule this out.
If all hosts except for the host in maintenance are full or close to full, you will need to contact our OVHcloud Support Engineers in order for a spare to be provisioned during this reboot window.
If sufficient space is available on your additional host(s), please see the below troubleshooting steps.
Affinity rules are in place
Click on your cluster that contains the host in maintenance mode.
Navigate to the "Configure" Tab for the cluster. then navigate to Configuration>VM/Host Rules.
If Affinity Rules are in place, you will see rules as shown below. highlight a rule and click edit.
Click the "Enable rule" checkbox to disable the rule. Please note that you will need to do this for each rule if multiple rules exist in your environment.
The automation should now be able to continue moving forward. The disabled affinity rules will need to be enabled after the host reboots.
Attached devices/ISO's on VM(s)
If you receive an error similar to the one below, this could be 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/ISO. and select Actions>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 a device is mounted, The device will need to be disconnected by unchecking the "connected" checkbox.
If the migration task is still stuck after verifying these, Vmotion will need to take place manually.
Navigate to you host that is 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 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.
You will be prompted with the migration screen. Verify that "change compute resource only" is selected and click Next.
Select the host that you would like to migrate the VMs to and click next. Resources will need to be available on your additional host in order for the migration to proceed.
Select the network that your VMs need to be on and click next.
The next screen with show you the progress of the migration. Once complete, you will be able to reboot your host for the upgrade.
Should you have technical questions when reviewing or finding any host-level errors, you can always create a support request for our Cloud Support Engineers at any time in your OVHcloud Control Panel.