Updating an ESXi host image fails "Failed to run health checks for NSX-T"

Products

• VMware NSX

Issue/Introduction

• You are trying to update an ESXi host image.
• Running health checks for NSX-T on vLCM cluster fails with error: Failed to run health checks for NSX-T
• Log lines similar to the below are encountered on vCenter Server in /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log:

  error vmware-vum-server[256####] [Originator@6876 sub=EHP opID=########-####-####-####-############] Response from localhost/external-tp/http1/##.##.##.##/443/########################################/api/v1/vlcm/esx/health/cluster/perspectives/ready-for-apply/status?action=check: HTTP Status:500 'Internal Server Error'

• Log lines similar to the below are encountered on NSX Manager in /var/log/proxy/reverse-proxy.log:

  ERROR https-jsse-nio-##.##.##.##-443-exec-558698 BaseProxyDelegate 72690 - [nsx@6876 comp="nsx-manager" errorCode="MP215" level="ERROR" subcomp="http"] Cannot make a query to server: http://127.0.0.1:7442/upgrade-coordinator/api/v1/vlcm/esx/health/cluster/perspectives/ready-for-apply/status?action=check
  org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:7442 [/127.0.0.1] failed: Connection refused (Connection refused)

• Log lines similar to the below are encountered on NSX Manager in /var/log/upgrade-coordinator/upgrade-coordinator-tomcat-wrapper.log:

  | JVM received a signal SIGKILL (9).
  | JVM process is gone.
  | JVM exited unexpectedly.

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

Cause

If the upgrade-coordinator is crashed and didn't automatically restart, it cannot serve the validation request from the vCenter.

Resolution

Reboot the affected NSX Manager appliance to restore the upgrade-coordinator service.