SDDC Management Domain: Online Depot Bundles Not Displayed in Available Updates When 5.2.1.0 is Selected

Products

• VCF Operations

Issue/Introduction

The Management Domain's Available updates option does not reflect Downloaded bundle once the 5.2.1.0 is selected

Environment

VCF 4.x
VCF 5.x

Cause

This issue occurs due to a version mismatch in the SDDC Manager database. The ESXi version (and potentially other component versions) for the Management and/or Workload Domains is reflected incorrectly in the SDDC Manager UI and database, even though the actual version is equal to or higher than the required VCF BOM level.

The assessment of deployment versions applies across both the Management Domain and Workload Domains. Therefore, when upgrading to VCF 5.2.1.0, all VCF components must meet or exceed the VCF 4.5.2 BOM level.

lcm-debug.log
yyyy-mm-ddT06:44:13.817+0000 DEBUG [vcf_lcm,bbd0d72d####4864,779c] [c.v.e.s.l.a.i.InventoryClientHelper,http-nio-###.0.0.1-7400-exec-5] Deployment VCF version is 4.4.1.1
yyyy-mm-ddT06:44:13.834+0000 DEBUG [vcf_lcm,bbd0d72d####4864,779c] [c.v.e.s.l.d.c.m.LcmManifestClientImpl,http-nio-###0.0.1-7400-exec-5] Found manifest with version 1 and sequence number 105
yyyy-mm-ddT06:44:13.841+0000 WARN [vcf_lcm,bbd0d72d####4864,779c] [c.v.e.s.l.s.i.LcmManifestServiceImpl,http-nio-###.0.0.1-7400-exec-5] Deployment VCF version {"version":"4.4.1.1"} is below the minimum compatible VCF version of target VCF version {"version":"5.2.1.0"}

Note: The ESXi version cited (e.g., ESXi 7.0 Update 3d) is only an example. This issue is not limited to a specific ESXi version and can occur with any version where the actual build is equal to or higher than the BOM but is reported incorrectly in SDDC Manager.

ESXi Version in SDDC Database:

• SSH to SDDC Manager, connect to the database and view the ESXi versions currently reflected in the database:
  • psql -U postgres -d platform -h localhost
\c platform
select id, hostname, name, status, version from host;
    

 

Resolution

Update the SDDC Manager database with the correct version in use.

As the resolution involves making changes to the SDDC database, please contact Broadcom Support for assistance in applying the fix safely.