SDDC Manager do not show any upgrade bundles for Workload Domain or Bundles are marked as "Future" in SDDC Manager Bundle Management

Products

• VMware Cloud Foundation

Issue/Introduction

To fix the issue with Bundle availability in SDDC Manager

Symptoms:
Update / Patches in SDDC Manager Workload Domain do not show any Available updates

 

SDDC Manager Bundle Management Shows Bundle Availability status as "Future"



/var/log/vmware/vcf/lcm/lcm-debug.log shows the below error

2023-11-29T22:11:03.203+0000 ERROR [vcf_lcm,2eb45a6880171f82,eb49] [c.v.e.s.l.a.i.InventoryClientHelper,Scheduled-3] Failed to compare VRSLCM version with VCF 4.0.0.0 BOM version in domain b38de8f4-####-####-####-299a870ca8f8

SDDC Manager UI do not show the build number for vRSLCM version

 

 

Environment

VMware Cloud Foundation 4.5.x
VMware Cloud Foundation 4.x

Cause

Missing vRSLCM version build number in SDDC Inventory. 
The issue occurs when a number of post upgrade scripts fail to execute in vRSLCM

Resolution

This issue is resolved in VMware Aria Suite Lifecycle 8.12 Patch 2. See VMware Aria Suite Lifecycle 8.12 Patch 2 Release Notes for additional information.

Note: To avoid encountering this issue when upgrading to 8.14, it is recommended to first apply 8.12 Patch 2, otherwise, see the Workaround below for additional information.

Workaround:
Follow the below KB to fix the issue in vRSLCM

• After upgrading VMware Aria Suite Lifecycle 8.12 to 8.14 the Build and Version numbers are not updated

Follow the below steps to fix the issue in SDDC Manager inventory

1. Find the vRSLCM version and build number from vRSLCM UI
2. Take snapshot of SDDC Manager VM
3. ssh to SDDC Manager with vcf user and su to root
4. Run the below psql query to list vrslcm details from sddc platform database with missing build number in version
   • psql -h localhost -U postgres -d platform -c "select * from vrslcm;"
     • Sample output
5. Run the below psql command to update the vRSLCM build number found in Step # 1
   • psql -h localhost -U postgres -d platform -c "update vrslcm set version='<version-build number>'" 
6. Re-run psql query from Step # 4 and it should show the version and build number
   • Sample output 
   • 
7.  Restart lcm service
   • systemctl restart lcm

Additional Information

Impact/Risks:

Not able to upgrade the components of any domain.