Similar errors are found in the SDDC U.
Retrieving all applicable bundles failed. Encountered fetching http://127.0.0.1/lcm/inventory/upgrades api - No enum constant com.vmware.evo.sddc.lcm.model.bundle.BundleSoftwareType.MULTI_SITE_SERVICE
Retrieving available bundles failed. Unable to retrieve aggregated domains upgrade status: Encountered fetching http://127.0.0.1/lcm/inventory/upgrades api - No enum constant com.vmware.evo.sddc.lcm.model.bundle.BundleSoftwareType.MULTI_SITE_SERVICE
Similar errors are found in the lcm.log
/var/log/vmware/vcf/lcm/lcm.log
2023-11-09T16:45:30.781+0000 INFO [vcf_lcm,78fff01544dc1311,df27] [c.v.e.s.l.s.i.UpgradeAvailabilityServiceImpl,Scheduled-9] bundle 39759b15-d985-4c15-85d6-7d44fd24df45, 5.3.10-198939 will be available. Rest will be pending
2023-11-09T16:45:30.796+0000 ERROR [vcf_lcm,0000000000000000,0000] [o.s.s.s.TaskUtils$LoggingErrorHandler,Scheduled-9] Unexpected error occurred in scheduled task
java.lang.IllegalArgumentException: No enum constant com.vmware.evo.sddc.lcm.model.bundle.BundleSoftwareType.MULTI_SITE_SERVICE
Support for the MULTI_SITE_SERVICE bundle type was removed in 5.1 release. If environments still have stale MULTI_SITE_SERVICE bundle types from earlier releases of VCF it causes an issue with the lcm service.
3.Run the bundle_cleanup.py against the returned bundle ids.
/opt/vmware/vcf/lcm/lcm-app/bin/bundle_cleanup.py <bundle_id>
Example:
/opt/vmware/vcf/lcm/lcm-app/bin/bundle_cleanup.py 4162045d-0b25-4ca3-8e38-0371908ed9e6 df3c4a11-cca4-4cad-b776-35f2035633dd