Scheduling upgrade from VCF 5.2.0.0/5.2.0.1 to 5.2.1.1 or 5.2.1.2 fails with Error that "One or more bundles require download for the upgrade"

Products

• VMware SDDC Manager

Issue/Introduction

There are two potential symptoms with regards to missing SDDC Manager 5.2.1.0 bundle, BOM bundles that hinders scheduling update of SDDC-M 5.2.1.1 or 5.2.1.2 Express patches

•  SDDC Manager 5.2.1.0 complaining with message "One or more bundles require download for the upgrade: {0}" and is shown in SDDC Manager UI when 5.2.1.1 or 5.2.1.2 bundle is attempted to be scheduled.
  
  OR
  
  
•  SDDC manager complains about missing BOM bundle for 5.2.1.0, it's mentioned in the release notes but it doesn't explain how to download it explicitly. When we create a new plan patch (to download 5.2.1.0), it still downloads the latest bundle and not 5.2.1.0 (which was selected in plan patch)  i.e, One or more bundles require download for the upgrade: {0}  error is bubbled up to SDDC UI when SDDC-M 5.2.1.1 or 5.2.1.2 bundle is attempted to be scheduled
  
  
  
•  LCM logs shows the following error message:
  2025-03-21T20:08:16.346+0000 ERROR [vcf_lcm,7d961b0b8ecf4157,cb34] [c.v.v.l.r.a.c.v.u.UpgradeController,http-nio-127.0.0.1-7400-exec-6] Scheduling Upgrade Failed
com.vmware.evo.sddc.lcm.model.error.LcmException: One or more bundles require download for the upgrade: 5.2.1.0=[1836c2da-705c-4119-b3fa-1edba91a72d9, 4aac682c-ecf1-4828-acf8-1ceb466c2f9f, 1c145a20-1f19-4393-bec3-b424d12245b5, 7a70a555-74ec-4849-89d4-3e45b551c8d8]

Environment

VCF 5.2

VCF 5.2.0.1

VCF 5.2.1.0

Cause

SDDC Manager releases 5.2.1.1 and 5.2.1.2 are decoupled, meaning that the VCF release remains at 5.2.1 even though the SDDC Manager version is higher. Consequently, the SDDC Manager 5.2.1.1 and 5.2.1.2 bundles still contain the VCF 5.2.1 release. LCM assumes that the VCF 5.2.1.0 release BOM bundles are registered with the environment. As a result, the schedule API fails, displaying the error message "One or more bundles require download for the upgrade" to alert customers that additional bundles need to be downloaded. This error message can appear on both the Plan Patch and SDDC Manager screens.

Resolution

Resolution 1:

Download and upload the SDDC-M 5.2.1.0 bundle:

• For online environments:

1. Navigate to the Bundle Management tab on the SDDC UI.
2. Download the bundle with the following ID: 1836c2da-705c-4119-b3fa-1edba91a72d9 (Bundle Name: bundle-133760).

• For offline environments:

1. Utilize the Offline Bundle Transfer Utility (OBTU) to download and upload the SDDC-M 5.2.1.0 bundle.
2. Refer to the following documentation for detailed instructions on using OBTU: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-5-2-and-earlier/5-1/vmware-cloud-foundation-lifecycle-management/single-instance-topology-upgrade-sequence-lifecycle/downloading-vmware-cloud-foundation-bundles-lifecycle/offline-download-of-vmware-cloud-foundation-5-2-upgrade-bundles-lifecycle/bundle-transfer-utility-additional-options-lifecycle.html 

 

Resolution 2:

Note: If the environment is pre-patched with VC, ESX, and NSX components at versions higher than the VCF 5.2.1.0 BOM, follow these steps:

1. Identify the VCF release for the management domain.
2. Login as root user on the SDDC Manager.
3. Modify the LCM application properties:
   1. Navigate to /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties.
   2. Update the following properties:
      vcenter.install.version=8.0.3.00100-24091160
esx.install.version=8.0.3-24022510
nsxt.install.version=4.2.0.0.0-24105817
      
      
      
4. Restart the LCM service.
5. Validate bundles for the deployment:
   1. Online deployments: Ensure that the following bundles are registered with LCM by checking the Bundle Management tab:
      1836c2da-705c-4119-b3fa-1edba91a72d9
4aac682c-ecf1-4828-acf8-1ceb466c2f9f
1c145a20-1f19-4393-bec3-b424d12245b5
7a70a555-74ec-4849-89d4-3e45b551c8d8
   2. Offline deployments: Use OBTU to download and upload the SDDC Manager bundle (bundle-133760) and the 5.2.1 BOM bundles.
      1. To avoid downloading the complete BOM bundles, download and upload the bundle manifests instead:
         Download bundle manifests:
         ./lcm-bundle-transfer-util --download --bundleManifests --depotUser ${DEPOT_USER}
         Transfer artifacts from DM-Z to SDDC-M.
         Upload bundle manifests:
         ./lcm-bundle-transfer-util --upload --bundleManifests --outputDirectory ${absolute-path-bundle-dir}
         Revert LCM application changes:

Note: If the LCM application properties were updated in step #3, revert these changes.