Upgrading the ESXi host with a custom image (8.0.3ug) through SDDC 5.X completed with the Standard Image instead

Products

• VMware SDDC Manager

Issue/Introduction

• Custom image using baselines was used for the ESXi host upgrade to 8.0.3ug
• Instead of a custom image, standard image was taken
• 
• The Bundle-ID used for the upgrade was the BOM version 8c0de63d-b522-4db8-be6c-f1e0ab7ef554

Environment

VMware SDDC Manager 5.X

VMware vSphere ESXi 8.0.3

 

Cause

• Incorrect Bundle-ID used for the upgrade
• There are two different bundles for the same version ESX_HOST-8.0.3-24859861 with the Async Bundle-ID and BOM Bundle-ID. The BOM Bundle-ID has been used instead of the Async.

Resolution

1. Download the correct bundle with the correct Bundle-ID. 
   • You can retrieve the bundle ID by navigating to the Lifecycle Management/Bundle Management page and clicking View Details to view the Bundle-ID.
     For example, 8c0de63d-b522-4db8-be6c-f1e0ab7ef554. The Bundle-ID for an async patch looks slightly different. For example: 5dc57fe6-2c23-49fc-967c-0bea1bfea0f1-apTool. Read more at Upgrade ESXi with Custom ISOs
2. Once bundle has been downloaded disconnect the depot to disable depot requesting the incorrect Bundle-ID to be used for the upgrade
3. Clean the old downloaded bundle from SDDC manager ssh with below command. In our case the incorrect bundle ID is 8c0de63d-b522-4db8-be6c-f1e0ab7ef554

   python /opt/vmware/vcf/lcm/lcm-app/bin/bundle_cleanup.py 8c0de63d-b522-4db8-be6c-f1e0ab7ef554 
   

4. Get the manifest file from the API through Developer Center API Explorer and paste it into the notepad
   Change the incorrect Bundle-ID with the correct Bundle-ID
   Copy the file and post it into the Manifest API in API Explorer
5. Upgrade the ESXi hosts 
   Note, the ESXi hosts that have already being upgraded with the Standard image will not be taken into consideration when upgrading at this time, instead upgrade the ESXi hosts through the vCenter and then synchronize the inventory in SDDC with this KB Synchronize inventory versions after out-of-band upgrade in a VMware Cloud Foundation Environment 
   
   
6. Once the above is done, Depot can be connected again