Applying configuration profile to a cluster fails in validating compliance with error: Desired configuration failed validation on the host. Check compliance is skipped.
search cancel

Applying configuration profile to a cluster fails in validating compliance with error: Desired configuration failed validation on the host. Check compliance is skipped.

book

Article ID: 416379

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • When trying to apply configuration profile to a cluster (Cluster --> Configure --> Desired State --> Configuration), the configuration compliance validation fails with the following error for one or more host.

Hostname

Desired configuration failed validation on the host. Check compliance is skipped.

Path

/host-override/4c#####-######-33/esx/storage/block_devices/0/hpp/mark_local

 

Environment

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

This issue is due to property mismatch in the ESXi host configuration file

Resolution

NOTE:

  • Since 7.0 U2 the service configuration settings are not stored in /etc/vmware/hostd/config.xml but in a special config store database.
  • The settings in the database are accessible by using /bin/configstorecli.

As per the path mentioned in the error message "/host-override/4c#####-######-33/esx/storage/block_devices/0/hpp/mark_local", validated the configuration in working and non-working ESXi host under storage block devices.

  • Check the storage configuration properties in the host file using the following command: /bin/configstorecli config current get -c esx -g storage -k block_devices

Example:

Non-working host:

Working host:

  • Place the host in Maintenance Mode
  • Copy the existing configuration to tmp.json file:
    • /bin/configstorecli config current get -c esx -g storage -k block_devices -outfile tmp.json
  • Delete the existing configuration using the following command:
    • configstorecli config current delete -c esx -g storage -k block_devices --all
  • Restart the host management agents:
    • /etc/init.d/hostd restart
    • /etc/init.d/vpxa restart
  • Apply the configuration profile at the cluster, it validates and completes successfully