vCenter async patch showing as future in an ONLINE vXrail environment

Products

• VMware SDDC Manager

Issue/Introduction

• Async patch for vCenter successfully downloaded using the Async Patch tool
• Async bundle is showing a 'Future' under Bundle Management
• Async patch may have been available for the Management domain but is not available for VI domain(s)

Environment

vXrail 4.5.x

Cause

The /nfs/vmware/vcf/nfs-mount/bundle/softwareCompatibilitySets.json does not contain the correct compat set.

Resolution

The VersionAlias file looks good 

 

However the lcm logs indicate that there is an issue with the softwareCompatibilitySets.json:

 

2024-10-20T10:56:16.293+0000 DEBUG [vcf_lcm,5e1a8e913de27dff,9096] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,
http-nio-127.0.0.1-7400-exec-6] Checking if application of bundle: c76103c3-aa88-43ba-a814-3909022df02a-apTool
 will result in invalid state for domain: b274c4c9-733a-458e-94dc-b6a09890f0cd
2024-10-20T10:56:16.293+0000 DEBUG [vcf_lcm,5e1a8e913de27dff,9096] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,
http-nio-127.0.0.1-7400-exec-6] Current domain compatibility : currentCompatibilitySet - 1.3.7-123456:7.0.3-21
930508:3.2.3.1.0-22104592
2024-10-20T10:56:16.293+0000 DEBUG [vcf_lcm,5e1a8e913de27dff,9096] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,
http-nio-127.0.0.1-7400-exec-6] compatibilitySetUnderCheck: compatibility for bundle-id c76103c3-aa88-43ba-a81
4-3909022df02a-apTool - compatibility 7.0.3.02100-24201990:7.0.3-21930508:3.2.3.1.0-22104592  <------!
2024-10-20T10:56:16.293+0000 DEBUG [vcf_lcm,5e1a8e913de27dff,9096] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,
http-nio-127.0.0.1-7400-exec-6] Update with bundle: c76103c3-aa88-43ba-a814-3909022df02a-apTool results in inv
alid state: true
2024-10-20T10:56:16.293+0000 INFO  [vcf_lcm,5e1a8e913de27dff,9096] [c.v.e.s.l.s.i.InventoryUpgradeServiceImpl,
http-nio-127.0.0.1-7400-exec-6] Removing VC: a70fc0d5-4185-4320-a8bf-79ac2c53c1fe from domain: b274c4c9-733a-4
58e-94dc-b6a09890f0cd update list of bundle: c76103c3-aa88-43ba-a814-3909022df02a-apTool, as it bundle applica
tion moves the Core SDDC Software State to non-supported state

From the above example we can see that lcm expects to see the following set in the softwareCompatibilitySets.json:

7.0.3.02100-24201990:7.0.3-21930508:3.2.3.1.0-22104592

where:

7.0.3.02100-24201990 is the TARGET vCenter build (i.e. the async patch)

7.0.3-21930508 is the CURRENT, running ESXi version

3.2.3.1.0-22104592 is the CURRENT, running NSXT version.

Manually amending the softwareCompatibilitySets.json and upolading the new set to lcm succeeds but does not resolve the issue - the async vCenter patch still shows as 'Future'

Also, the lcm logs continue to complain that the set is not included in the softwareCompatibilitySets.json file.

To resolve:

• Disable the async patch(es) - /home/vcf/asyncPatchTool/bin/vcf-async-patch-tool --disableAllPatches --sddcSSOUser SSOuser --sddcSSHUser vcf


• Enable the async bundle again - ./vcf-async-patch-tool -e --patch product:version --du broadcom_support_email --pdu dell_emc_depot_email --sddcSSOUser SSOuser --sddcSSHUser vcf --it ONLINE


• NOTE: If there is a proxy in play you will need to include the --proxyServer option

 

This process should amend the softwareCompatibilitySets.json as part of the download/enable workflow.