Error on vCenter server UI "Host status is unknown. The host could not be reached, and its image compliance could not be checked. Try refreshing image compliance again - the host may be reached successfully"
search cancel

Error on vCenter server UI "Host status is unknown. The host could not be reached, and its image compliance could not be checked. Try refreshing image compliance again - the host may be reached successfully"

book

Article ID: 395010

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vSphere ESXi 8.0 VMware vCenter Server

Issue/Introduction

  • Host patching/upgrade/compliance check fails while trying from vCenter server UI with the following error

    Host status is unknown. 
The host could not be reached, and its image compliance could not be checked. Try refreshing image compliance again - the host may be reached successfully.
During remediation, this host may get remediated if it can be reached successfully.

  • Staging or remediation of hosts will give the following error at cluster

Staging of cluster failed
<ESXI-FQDN> - Skipped stage for this host
 Skipped host <ESXI-FQDN> because its compliance information is unavailable. Please check the host status <ESXI-FQDN> - Skipped stage for this host
 Skipped host <ESXI-FQDN> because its compliance information is unavailable. Please check the host status <ESXI-FQDN> - Skipped stage for this host
 Skipped host <ESXI-FQDN> because its compliance information is unavailable. Please check the host status <ESXI-FQDN> - Skipped stage for this host
 Skipped host <ESXI-FQDN> because its compliance information is unavailable. Please check the host status <ESXI-FQDN> - Skipped stage for this host
 Skipped host <ESXI-FQDN> because its compliance information is unavailable. Please check the host status <ESXI-FQDN> - Skipped stage for this host

  • From the vmware-vum-server.log under /var/log/vmware/vmware-updatemgr/vum-server/ in vCenter server observed the following events-

YYYY-MM-DDTHH:MM:SST warning vmware-vum-server[#####] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask opID=29####13c-####-####-####-5408#####86aa] [Task, ######] Task:com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask ID:52###ab0-####-####-####-1790####bcf3. Status is still pending for host : <ESXI-FQDN> (host-####) ..Waiting.
YYYY-MM-DDTHH:MM:SST info vmware-vum-server[#####] [Originator@6876 sub=Ufa.HTTPService.HttpConnection] HTTP Connection has timed out while waiting for further requests; <io_obj p:0x00007fc0600fedd0, h:-1, <TCP '127.0.0.1 : 8086'>, <TCP '127.0.0.1 : 45692'>>, N7Vmacore16TimeoutExceptionE(Operation timed out: Stream: <io_obj p:0x00007fc0600fedd0, h:-1, <TCP '127.0.0.1 : 8086'>, <TCP '127.0.0.1 : 45692'>>, duration: 00:20:01.459279 (hh:mm:ss.us))
...
YYYY-MM-DDTHH:MM:SST warning vmware-vum-server[#####] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask opID=29####13c-####-####-####-5408#####86aa] [Task, ######] Task:com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask ID:52###ab0-####-####-####-1790####bcf3. Status is still pending for host : <ESXI-FQDN> (host-####) ..Waiting.
...
YYYY-MM-DDTHH:MM:SST info vmware-vum-server[#####] [Originator@6876 sub=StageClusterTask opID=29####13c-####-####-####-5408#####86aa] [Task, ######] Task:com.vmware.vcIntegrity.lifecycle.StageClusterTask ID:528###05-####-####-####-7#######1c0. Skipping unavailable host ID: host-####, Name: <ESXI-FQDN>
...
YYYY-MM-DDTHH:MM:SST error vmware-vum-server[#####] [Originator@6876 sub=VumVapi::Lib::Utils opID=29####13c-####-####-####-5408#####86aa] [Utils 1075] Cluster with ID: domain-#### is not vSAN enabled, cannot fetch witness host(s) for non-vSAN cluster. Returning empty set.
YYYY-MM-DDTHH:MM:SST error vmware-vum-server[#####] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask opID=29####13c-####-####-####-5408#####86aa] [Task, ######] Task:com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask ID:52###ab0-####-####-####-1790####bcf3. Host entry host-#### missing among image results.
YYYY-MM-DDTHH:MM:SST error vmware-vum-server[#####] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask opID=29####13c-####-####-####-5408#####86aa] [Task, ######] Task:com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask ID:52###ab0-####-####-####-1790####bcf3. Host entry host-#### missing among image results.
YYYY-MM-DDTHH:MM:SST info vmware-vum-server[#####] [Originator@6876 sub=VumVapi::Lib::Utils opID=29####13c-####-####-####-5408#####86aa] [Utils 1301] Deployment environment is UNKNOWN, going for detection. 
YYYY-MM-DDTHH:MM:SST error vmware-vum-server[#####] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask opID=29####13c-####-####-####-5408#####86aa] [Task, ######] Task:com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask ID:52###ab0-####-####-####-1790####bcf3. Host entry host-#### missing among image results.

Environment

  • VMware vSphere ESXi
  • VMware vCenter Server

Cause

This issue can occur due to the following causes:

  • Network/DNS issue between vCSA and ESXi hosts 
  • Failure while validating nslookup for vCenter FQDN/IP from host and vice-versa:
    • nslookup <VC-FQDN>
      connection timed out; no servers could be reached
  • If inbound connection on port 9084 towards the vCenter server from the ESXi host was not allowed:
    • nc -vz <VC-FQDN> 9084
      nc: connect to VC-FQDN port 9084 (tcp) failed: Connection timed out

Resolution

Powered by Wolken Software