OPERATIONAL DEFECT DATABASE
...
...
1. Description Reduced Downtime Upgrade (RDU) is a new mechanism introduced for upgrading the self-managed vCenter Servers with decreased downtime. Self-managed vCenter Server is one that manages its own ESXi host and its own virtual machine. This does not require a jump host to mount the ISO but the vCenter ISO needs to be mounted on the CD-ROM device of the vCenter Server Virtual Machine. The Workflow is integrated inside the vCenter Server itself. 2. Supported upgrade paths Source VersionTarget Version8.0 GA8.0 U2 or later releases8.0 U18.0 U2 or later releases8.0 P028.0 U2 or later releases8.0 U2Releases later than 8.0 U2 3. Known issues An error might be encountered which says "Update 8.0.x.xxxxxx for component vlcm is not found". To remediate this error, follow Patching vCenter to 8.0U2 using Update Planner fails with error "Update 8.0.2.00000 for component vlcm is not found".
Workflow 1. Download and mount ISO The ISO needs to be downloaded in the Content Library/Datastore which is connected to the vCenter Virtual Machine or in the content library of the Managing vCenter. Go to the properties of the vCenter Server Virtual Machine. Connect the VCSA ISO to CD-ROM by browsing the datastore/content library. Select the Connected checkbox and click OK. 2. Flow 1: Upgrade from version 8.0 GA, 8.0 U1, 8.0 P02 to 8.0 U2 Set the target in VAMI (vCenter Server Appliance Management Interface) while using the offline custom repository. If online repository is used, make sure that the Default Repository URL is selected. Go to Update Planner Select the Target 8.0 U2 version. Ensure the backup of the vCenter Server has been taken, then Perform Update Plugin from the Upgrade Planner page. Note: An error might be encountered which says "Update 8.0.x.xxxxxx for component vlcm is not found". To remediate this error, follow Patching vCenter to 8.0U2 using Update Planner fails with error "Update 8.0.2.00000 for component vlcm is not found"Once the plugin is upgraded the page will refresh to load the new UI. The new UI should reload with ISO options There is a discard functionality in the workflow. This can be used to discard all information which has been currently entered in the workflow. Note: This does not revert the "Upgrade Plugin" Mount the Target 8.0 U2 ISO on the vCenter. Please refer to Download and mount ISO for more information. On the Update planner page the ISO File gets updated with the current version, proceed to next Ensure the backup is completed. No Update Plugin required and Prepare Target should be enabled Please read and accept the License Agreement. Join the Customer Experience Improvement Program (CEIP) Target location ( Deploy in same location as source) . The configuration with which you can deploy the target vCenter which can be the same configuration as source or user can select the detailed configuration. Select the datacenter or Virtual Machine Folder where the target vCenter Server needs to be deployed Select the Compute Resource to deploy the target vCenter Server. This contains the Virtual Machine name and temporary root password. However post upgrading the same root password as source will be applied. The source machine deployment size is displayed here based on this the user can select the Deployment Size for the target. Note: The Deployment size configuration can be same or greater than the source. Select the target Datastore location where the vCenter Server will be deployed. Network Settings Review and proceed with Finish. The configuration for the target (upgraded) vCenter server is now saved. Proceed to upgrade steps. Once the prepare target is complete, user can click on switchover. This operation will include downtime of around 10 mins. There is an option to “Cancel upgrade” . Once clicked on this, the upgrade will be cancelled and can be triggered again. Switchover: Do not close this window or else we would not see any progress of the upgrade. The switchover is the step where source vCenter Server configuration is applied to the target vCenter Server and the target vCenter Server starts all the services on it to start accepting requests. 3. Flow 2: Upgrade from version 8.0 U2 to later than 8.0 U2 Go to Update Planner, The new UI should load with the ISO options Continue to Backup, Update Plugin steps Mount the Target 8.0 U2 ISO on the VC. Please refer to ISO downloading and mounting for more information. Update the Plugin to the version later than 8.0 U2 from the ISO, page gets refreshed post this. Prepare Target should be enabled Please read and accept the license agreement. Join the Customer Experience Improvement Program Target Location The configuration with which you can deploy the target vCenter which can be the same configuration as source or user can select the detailed configuration. Select the datacenter or Virtual Machine Folder where the target vCenter Server needs to be deployed Select the Compute Resource to deploy the target vCenter Server. This contains the Virtual Machine name and temporary root password. However post upgrading the same root password as source will be applied. The source machine deployment size is displayed here based on this the user can select the Deployment Size for the target. Note: The Deployment size configuration can be same or greater than the source. Select the target Datastore location where the vCenter Server will be deployed. Network Settings Note: Mac Changes is set to 'Reject' on portgroups VM Network used by the vCenter. Forged Transmits is set to 'Reject' on portgroups VM Network used by the vCenter. This could prevent from a successful upgrade. Review and confirm the data The configuration for the target (upgraded) vCenter server is now saved. Proceed to upgrade steps Once the prepare target is complete, user can click on switchover. This operation will include downtime of around 10 mins. There is an option “Cancel upgrade” as well. Once clicked on this, the upgrade will be cancelled and can be triggered again. Switchover: Do not close this window or else we would not see any progress of the upgrade. The switchover is the step where source vCenter Server configuration is applied to the target vCenter Server and the target vCenter Server starts all the services on it to start accepting requests. Cancellation After failed upgrade If the upgrade fails, the upgrade will automatically revert to the source machine and bring it to the state it was in before the upgrade. There is no action required from the user.The logs should be collected using Collecting diagnostic information for VMware vCenter Server 4.x, 5.x, 6.x and 7.0 and send to VMware Support to open a ticket. After successful upgrade It is important to note that upon canceling the upgrade, the target vCenter Server machine which is deployed, is automatically deleted.If for any reason, the user wants to revert to the source machine, they will need to power on the source machine, this will trigger the cancelation on the source machine and will delete the target machine. Miscellanous Important Disconnect the network adapter of the source VCSA VM after the successful upgrade. This is required because of the current functionality of the source VM that if powered on, deleted the target VM. Unsupported topologies TopologySource VersionTarget VersionUser Visible BehaviorSupport ETAVCHA8.0, 8.0u18.0 u2Future Patch Release.Uber Managed8.0, 8.0u18.0 u2Future Patch Release.ELM8.0, 8.0u18.0 u2Future Patch Release.DUAL IP Stack8.0, 8.0u1, 8.0u2 Future Patch Release.Deploy on ESXi8.0, 8.0u1, 8.0u28.0u2 and 8.0 u2+Future Patch Release. Disclaimers i. Users should not be using multiple lifecycle operations at the same time. for example, they should not use Reduced downtime upgrade and VAMi at the same time. This may interfere in already running lifecycle event and may lead to corrupt vCenter Server. ii. If the ISO is mounted from the Reduced downtime upgrade workflow, VAMI (vCenter Server Appliance Management Interface) should not be used to upgrade the vCenter Server as it is not patch iso which is used to update the vCenter Server to the minor version update.iii. Only single administrator should be performing the Reduced downtime upgrade workflow at any given point in time
Patching vCenter to 8.0U2 using Update Planner fails with error "Update 8.0.2.00000 for component vlcm is not found"
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
