After upgrading VCF SDDC Manager from 4.1 to 4.2, incorrect BoM bundles are shown as available for upgrade.

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:
Note: This is applicable for offline VxRail deployments only

After performing skip level upgrade from VCF 4.1.0.0 to 4.2.0.0 one ore more of the following symptoms is observed:

• In SDDC Manager UI under "Update/Patches" section of Management / Workload domains

1. VxRail 7.0.101 bundle is shown as available
2. Upgrade bundles of BoM components for 4.2.0.0 (NSX-T) are not shown as available

• Also verify following:

1. Version alias file (/opt/vmware/vcf/lcm/lcm-app/confVersionAlias.yml) has below entries:

 

versionAliases:
  ESX_HOST:
  - alias:
    - 7.0.1-16850804
    base: 7.0.1-17168206

2. LCM debug log has messages as below:

2021-08-10T15:30:44.846+0000 DEBUG [vcf_lcm,8d6e2d745b7e4592,927d] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,http-nio-127.0.0.1-7400-exec-10] min ESX version found before alias translation is 7.0.1-16850804
2021-08-10T15:30:44.847+0000 DEBUG [vcf_lcm,8d6e2d745b7e4592,927d] [c.v.e.s.l.s.UpgradeServiceHelper,http-nio-127.0.0.1-7400-exec-10] The version 7.0.1-16850804 is a base version already and not among allowable list for aliasing
2021-08-10T15:30:44.847+0000 DEBUG [vcf_lcm,8d6e2d745b7e4592,927d] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,http-nio-127.0.0.1-7400-exec-10] min ESX version found after alias translation is 7.0.1-16850804

Environment

VMware Cloud Foundation 4.1

Cause

Issue occurs due to version aliasing not getting applied for ESXi versions on offline VxRail deployments.

Resolution

Issue is fixed in VCF 4.3.0.0.

Workaround:
After performing skip level upgrade from 4.1.0.0 to 4.2.0.0, download the updated compatibility sets file from VMware depot and upload to SDDC Manager.

Please refer to Broadcom Techdocs for usage of bundle transfer utility to download and upload compatibility sets.