SDDC Manager Updates Tab has Errors After Upgrade to 5.2.x - "Getting Upgradable API call failed" and "Retrieving update patches bundles failed"

Products

• VMware SDDC Manager

Issue/Introduction

• After upgrading SDDC Manager from version 5.1.x to 5.2.x, users may encounter errors when attempting to access the Updates tab in the SDDC Manager UI. These errors prevent the system from properly retrieving and displaying available updates and patches.

• Users will see one or both of the following errors displayed in the SDDC Manager UI Updates tab:

  • "Getting Upgradable API call failed. Something went wrong. Please retry or contact the service provider and provide the reference token."

  • "Retrieving update patches bundles failed. Unable to retrieve aggregated LCM bundles. Error in getDomainBomVersion(): Encountered error requesting http://127.0.0.1/v1/system/upgradables api. Something went wrong. Please retry or contact the service provider and provide the reference token."

• References from /var/log/vmware/vcf/lcm/lcm.log:

YYYY-MM-DDT21:54:58.949+1000 ERROR [vcf_lcm,0000000000000000,0000] o.a.c.c.C.[.[.[.[dispatcherServlet],http-nio-127.0.0.1-7400-exec-6] Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: java.lang.RuntimeException: Target VCF version 5.1.0.0 is lower than source VCF version 5.1.1.0] with root cause
java.lang.RuntimeException: Target VCF version 5.1.0.0 is lower than source VCF version 5.1.1.0
YYYY-MM-DDT21:54:58.950+1000 ERROR [vcf_lcm,693419922ddb4121ea26f3be47f7cc8d,be6b] [c.v.e.s.e.h.VcfFallbackErrorController,http-nio-127.0.0.1-7400-exec-6] [GRKSK5] - Error attributes: {timestamp=Sat Dec 06 21:54:58 AEST 2025, status=500, error=Internal Server Error, exception=java.lang.RuntimeException, trace=java.lang.RuntimeException: Target VCF version 5.1.0.0 is lower than source VCF version 5.1.1.0
        at com.vmware.evo.sddc.lcm.services.impl.LcmManifestServiceImpl.getBundleComponentsPair(LcmManifestServiceImpl.java:1534)
        at com.vmware.evo.sddc.lcm.services.impl.LcmManifestServiceImpl.getBundleComponentsPair(LcmManifestServiceImpl.java:1513)
        at com.vmware.evo.sddc.lcm.services.impl.LcmManifestServiceImpl.getVmwBundlesForSkipUpgrade(LcmManifestServiceImpl.java:1082)
        at com.vmware.evo.sddc.lcm.services.vvs_availabilty.impl.BomBundlesAvailabilityServiceImpl.findDomainBundles(BomBundlesAvailabilityServiceImpl.java:197)
        at com.vmware.evo.sddc.lcm.services.vvs_availabilty.impl.BomBundlesAvailabilityServiceImpl.findDomainBundlesInOrder(BomBundlesAvailabilityServiceImpl.java:74)
        at com.vmware.evo.sddc.lcm.services.vvs_availabilty.impl.CurrentTargetVersionBomBundlesAvailabilityImpl.findDomainBomBundlesInOrder(CurrentTargetVersionBomBundlesAvailabilityImpl.java:57)

Environment

SDDC Manager 5.1.x

SDDC Manager 5.2.x

Cause

The issue is typically caused by conflicting target version entries or stale entries remaining in the SDDC Manager database, specifically within the lcm service database. These erroneous entries might originate from any of the managed nodes (such as vCenter, ESXi, NSX, etc.).

To validate, check the output of below command;

# psql -h localhost -U postgres lcm -c "select * from domain";

Example below; 

target_version |                  id                  | target_vxrail_version |      creation_time      |    modification_time    | target_sddc_manager_version | target_esx_version | target_nsx_version | target_vc_version
 ----------------+--------------------------------------+-----------------------+-------------------------+-------------------------+------------- ----------------+--------------------+--------------------+-------------------
  5.1.0.0        | #######-####-#####-####-############ |                       | 2024-07-08 14:29:21.125 | 2024-07-08 14:29:21.125 | 5.1.0.0-22688368            |                    |                    |
  5.2.2.0        | #######-####-#####-####-############ |                       | 2024-07-02 07:48:34.225 | 2025-12-06 17:28:52.137 | 5.2.2.0-24936865            |                    |                    |

Date and Time will vary in each environment.

In this example, SDDC manager was upgraded to 5.2.x, however we had a stale entry in database for 5.1.x version.

Resolution

Manual cleanup of entries from SDDC database is required to fix the issue. As editing the database is destructive in nature, we suggest in raising a Support Case with Broadcom.