"Compliance check failed or skipped" on a cluster managed with a single image.
search cancel

"Compliance check failed or skipped" on a cluster managed with a single image.

book

Article ID: 373510

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms

  • On a cluster managed with a single image and using vSphere Configuration Profiles, you can see the error message:  "Compliance check failed or skipped on esxi_hostname".
  • In vCenter log file vmware-vum-server.log, you can see lines similar to:

<timestamp> info vmware-vum-server[26500] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CheckComplianceTask] [ConfigurationHandlers 1232] Detected ConfigManager unlicensed host: <esxi_hostname>
<timestamp> error vmware-vum-server[26500][Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.CheckComplianceTask] [Task, 511] Task:com.vmware.vcIntegrity.lifecycle.CheckComplianceTask ID:52f7fd5e-d33b-71ba-12d6-1bbd2a8bb7b8. Task Failed. Error: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.ConfigurationCheckComplianceTask.Failure<Compliance check failed or skipped on '<esxi_hostname>'.>

Environment

  • vCenter Server 8.x
  • vCenter Server 7.x

Cause

ESXi are not license at the correct level

https://core.vmware.com/resource/configuration-management-using-vsphere-configuration-profiles

Cluster hosts must be licensed with Enterprise Plus license.

Resolution

 

  •  assign a compatible license to ESXi

OR

  • Workaround: Create a new cluster without using vSphere Configuration Profiles (Manage configuration at a cluster level option)

Additional Information

Powered by Wolken Software