This article provides steps to validate the error message as seen in Updates tab and further correlate the same in lcm-debug logs. To resolve the issue, it has been suggested to open a Support ticket with Broadcom.
"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."
/var/log/vmware/vcf/lcm/lcm-debug.logThe logs show entries similar to 'Target VCF version 5.1.0.0 is lower than source VCF version 5.2.1.0'
YYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_lcm,68dd6d170c8e6a8c0503be35c74f4316,3317] [c.v.e.s.l.s.i.LcmManifestServiceImpl,Scheduled-3] Current vcfWithVxRailDomainVersions map from inventory: {5.2.1.0=[8.0.322-###]}YYYY-MM-DDTHH:MIN:SEC DEBUG [vcf_lcm,68dd6d170c8e6a8c0503be35c74f4316,3317] [c.v.e.s.l.s.i.LcmManifestServiceImpl,Scheduled-3] VxRail include list for version: 5.2.1.0 : [8.0.310-###]YYYY-MM-DDTHH:MIN:SEC ERROR [vcf_lcm,68dd6d170c8e6a8c0503be35c74f4316,3f6f] [c.g.common.eventbus.EventBus.default,Scheduled-3] Exception thrown by subscriber method recieveMessage(com.vmware.evo.sddc.lcm.model.task.AbstractLcmControllableScheduledTask) on subscriber com.vmware.evo.sddc.lcm.core.scheduler.BundleDownloadScheduler@4740e12f when dispatching event: com.vmware.evo.sddc.lcm.core.scheduler.BundleDownloadScheduler@4740e12fjava.lang.RuntimeException: Target VCF version 5.1.0.0 is lower than source VCF version 5.2.1.0 at com.vmware.evo.sddc.lcm.services.impl.LcmManifestServiceImpl.getBundleComponentsPair(LcmManifestServiceImpl.java:1532) at com.vmware.evo.sddc.lcm.services.impl.LcmManifestServiceImpl.getBundleComponentsPair(LcmManifestServiceImpl.java:1511)
VCF 5.x
The issue can be due to conflicting target version entries mentioned in its database. The entries can be from any of its managed nodes, such as vCenter, ESXi, NSX,.etc.
Manual cleanup of entries from SDDC database is required. As editing the database is destructive in nature, we suggest in raising a Support Case with Broadcom.
Please refer to Broadcom article to raise a Support Case Creating and managing Broadcom support cases