vCenter Server reports host profile compliance error

Products

• VMware vSphere ESXi

Issue/Introduction

Apply the ESXi patch if you experience issues after removing the Auto Deployed ESXi host from the vCenter Server host.

Symptoms:
After removing an Auto Deployed ESXi host from the vCenter Server inventory and rebooting the ESXi host, you experience these symptoms:

• vCenter Server reports host profile compliance errors.
• The ESXi host fails to configure until rebooted again.
• In the /var/log/hostd.log file, you see entries similar to:
  
  <YYYY-MM-DD>T<time> [FFE1D5C0 error 'Vimsvc.ha-license-manager'] LoadLicense: The evaluation period is over
  <YYYY-MM-DD>T<time> [FFE1D5C0 info 'Vimsvc.ha-license-manager'] HaLicense: instance created
  <YYYY-MM-DD>T<time> [FFE1D5C0 verbose 'Default'] GetLicenseManager: returning HaLicense @0x1fc902e0 = {LicFeature @0x1fc77050 = { _daysLeft = 0, appha = 0, autodeploy = 0, das = 0, dpvmotion = 0, dr = 0, drs = 0, dvs = 0, endpoint = 0, esxHost = 0, ft = 0, hostprofile = 0, hotplug = 0, maxCPUs = 0, maxRamAllVMs = 0, maxRamPerVm = 0, maxRunningVms = 0, metrovmotion = 0, mpio = 0, rem = 0, replication = 0, serialuri = 2, sioshares = 0, smartcard = 0, spbm = 0, sriov = 0, storagedrs = 0, svmotion = 0, vaai = 0, vflash = 0, viewaccel = 0, vimapi = 0, vmotion = 0, vmsafe = 0, vshield = 0, vsmp = 0, vstorage = 0, }, _latency: 0_calls: 0}, how: construct
  </time></time></time>
  
• The ESXi host does not enter maintenance mode due to the expired license:
  
  <YYYY-MM-DD>T<time> [68481B70 info 'Solo.Vmomi' opID=hostd-214a user=vpxuser] Activation [N5Vmomi10ActivationE:0x68d1fac0] : Invoke done [enterMaintenanceMode] on [vim.HostSystem:ha-host]
  <YYYY-MM-DD>T<time> [68481B70 verbose 'Solo.Vmomi' opID=hostd-214a user=vpxuser] Arg timeout:
  --> 1200
  <YYYY-MM-DD>T<time> [68481B70 verbose 'Solo.Vmomi' opID=hostd-214a user=vpxuser] Arg evacuatePoweredOffVms:
  --> (null)
  <YYYY-MM-DD>T<time> [68481B70 verbose 'Solo.Vmomi' opID=hostd-214a user=vpxuser] Arg maintenanceSpec:
  --> (null)
  <YYYY-MM-DD>T<time> [68481B70 info 'Solo.Vmomi' opID=hostd-214a user=vpxuser] Throw vim.fault.RestrictedVersion
  <YYYY-MM-DD>T<time> [68481B70 info 'Solo.Vmomi' opID=hostd-214a user=vpxuser] Result:
  --> (vim.fault.RestrictedVersion) {
  --> dynamicType = <unset>,
  --> faultCause = (vmodl.MethodFault) null,
  --> msg = "",
  --> }</time></time></time></time></time></time>

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.5
VMware vSphere ESXi 5.0

Cause

This issue occurs when the ESXi host license association is removed after the ESXi host is removed from the vCenter Server inventory.

The Auto Deploy server attempts to provide the evaluation license for the ESXi host booted initially on the next reboot. However, if this is after 60 days from the first deployment, the evaluation period expires. This prevents the ESXi host to enter maintenance mode and results in host profile application failures.

Resolution

This is a known issue affecting ESXi 5.x.

This issue is resolved in ESXi 5.5, Patch Release ESXi550-201608001. For more information, see VMware ESXi 5.5, Patch Release ESXi550-201608001 (2144359).

To avoid this issue, do not remove Auto Deployed ESXi hosts from the vCenter Server inventory when they are rebooting.

To work around this issue, reboot the host a second time while it is in the vCenter Server inventory to fully configure the system.

Additional Information

vCenter Server 报告主机配置文件合规性错误
vCenter Server でホスト プロファイル コンプライアンス エラーが報告される