Deploying a WLD in VCF 9 fails at image compliance check on the vCenter with the error "The image on the host does not match the image set for the cluster"

Products

• VMware SDDC Manager

Issue/Introduction

• When creating a WLD, the sddc manager performs a compliance check of the imported custom image and the image installed on the host, and fails with the following error: 

After host 'esxi01.example.com' remediation completed, compliance check reported host as 'non-compliant'. The image on the host does not match the image set for the cluster. Retry the cluster remediation operation.
4 Software compatibility cannot be determined for release 9.0.0.0.24755229, 9.0.0.0.24755230. It can be either a security patch or an out-of-date compatibility data bundle having timestamp YYYY-MM-DDTHH:MM:SS. Firstly, please ensure the software compatibility data bundle is up-to-date. Please note that no software compatibility checks are performed on security patches.
esxi01.example.com - Failed to remediate host

• From the /var/log/vmware/vmware-updatemgr/vum-server/imageservice.log in the vCenter, the following error will be seen. 

YYYY-MM-DDTHH:MM:SS INFO imageService[139909227341504] [imageService 348] Error parsing zip:/storage/updatemgr/patch-store-temp/5e7c-8a7f-deb1-30cc.zip?metadata.zip: ('ESXi:9.0.0-0.24755229', 'baseimage', "Two baseimages share the same releaseID: ESXi:9.0.0-0.24755229, but have different attributes: versionSpec ('<VersionSpec version: 9.0.0-0.24755229; uiString: 9.0.0.0.24755229; vcfVersion: 9.0.0.0.24755229>' != '<VersionSpec version: 9.0.0-0.24755229; uiString: 9.0.0.0.24755229>')")

• Extracting the custom image and validating the base image JSON file in the path/VMware-VMvisor-Installer-CustomImage.zip_extracted/metadata.zip_extracted/baseimages/ESXi_9.0.0-0.24755229.json The following attributes will be observed: 

"versionSpec": {
      "version": "9.0.0-0.24755229",
      "uiString": "9.0.0.0.24755229"     
   }

• When a standard image or an OEM image from the Broadcom portal is inspected, at the path, VMware-VMvisor-Installer-9.0.0.0-24755229.x86_64-Dell-CI-A00.zip_extracted/metadata.zip_extracted/baseimages/ESXi_9.0.0-0.24755229.json The following attributes will be observed   

   "versionSpec": {
      "version": "9.0.0-0.24755229",
      "uiString": "9.0.0.0.24755229",
      "vcfVersion": "9.0.0.0.24755229"
   }

Environment

VCF 9 

Cause

The issue occurs if the custom images for VCF 9 are built using Power 13.3 or earlier, and the base image installed on hosts is built using a standard or OEM image from the Broadcom portal. 

• PowerCli 13.3 and earlier do not recognize the newly introduced attribute vcfVersion causing the final image to have only two attributes, as shown below, causing a disparity with the installed image and the Custom image. 

"versionSpec": {
      "version": "9.0.0-0.24755229",
      "uiString": "9.0.0.0.24755229"     
   }

 

Resolution

To resolve this issue, 

• Build Custom images using the VCF PowerCli 9. 
  • To build custom images using VC PowerCLI 9, please refer to: Creating a Custom ESX ISO Image Using VMware PowerCLI
• Ensure to build the ESXi hosts with the same image that is imported on the vCenter/SDDC manager.