Remediation of vSAN Cluster Failed due to vSAN Skyline Health Test in warning/error state

Products

• VMware vSphere ESXi
• VMware vSAN 7.x
• VMware vSAN 8.x
• VMware vSAN

Issue/Introduction

When using VMware vSphere Lifecycle Manager (vLCM) to remediate a vSAN cluster, the process may fail during the pre-check phase if the vSAN Skyline Health service reports warnings or errors. This article provides guidance on identifying and resolving these health check failures to allow remediation to proceed.

Symptoms:

• Remediation of vSAN Cluster fails during the pre-check.
• The following alerts may be flagged in vSAN Skyline Health:
  • vSAN HCL Health – vSAN HCL DB up-to-date (Warning: vSAN HCL DB not updated for 90+ days)
  • vSAN Health Service - Online Health - CEIP Check
• Lifecycle Manager reports: "Health Check for #### failed."

 

• Under /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log file, the following errors can be found:

  
  error vmware-vum-server[1677491] [Originator@6876 sub=RemediateClusterTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.RemediateClusterTask ID:<ID>
  ##-####-####-#####. Task Failed. Error: Error:
  -->    com.vmware.vapi.std.errors.error
  --> Messages:
  -->    com.vmware.vcIntegrity.lifecycle.TaskError.HealthCheckFailed<Health Check for 'vSAN-hardware-type-##' failed>
  -->
  2026-08-24T05:11:27.260-04:00 info vmware-vum-server[1677491] [Originator@6876 sub=PM.AsyncTask.RemediateClusterTask{898}] [vciTaskBase 1496] SerializeToVimFault fault:
  --> (vmodl.fault.SystemError) {
  -->    faultCause = (vmodl.MethodFault) null,
  -->    faultMessage = (vmodl.LocalizableMessage) [
  -->       (vmodl.LocalizableMessage) {
  -->          key = "com.vmware.vcIntegrity.lifecycle.TaskError.HealthCheckFailed",
  -->          arg = (vmodl.KeyAnyValue) [
  -->             (vmodl.KeyAnyValue) {
  -->                key = "1",
  -->                value = "vSAN-hardware-type-##"
  -->             }
  -->          ],
  -->          message = <unset>
  -->       }
  -->    ],
  -->    reason = "vLCM Task failed, see Error Stack for details."
  -->    msg = "{
  -->     "data": null,
  -->     "error_type": "ERROR",
  -->     "messages": [
  -->         {
  -->             "args": [
  -->                 "vSAN-hardware-type-##"
  -->             ],
  -->             "default_message": "Health Check for 'vSAN-hardware-type-##' failed",
  -->             "id": "com.vmware.vcIntegrity.lifecycle.TaskError.HealthCheckFailed"
  -->         }
  -->     ]
  --> }"
  --> }
  --> Converted fault:
  --> (vim.fault.ExtendedFault) {
  -->    faultCause = (vmodl.MethodFault) null,
  -->    faultMessage = (vmodl.LocalizableMessage) [
  -->       (vmodl.LocalizableMessage) {
  -->          key = "com.vmware.vcIntegrity.lifecycle.TaskError.HealthCheckFailed",
  -->          arg = (vmodl.KeyAnyValue) [
  -->             (vmodl.KeyAnyValue) {
  -->                key = "1",
  -->                value = "vSAN-hardware-type-##"
  -->             }
  -->          ],

Environment

• VMware vCenter Server 7.x / 8.x
• VMware vSAN 7.x / 8.x
• VMware vSphere Lifecycle Manager

 

Cause

Lifecycle Manager performs a mandatory pre-check of the vSAN cluster health before starting host remediation. If any health tests return a "Warning" or "Error" state, vLCM will block the remediation to prevent potential stability or data availability issues. An outdated vSAN Hardware Compatibility List (HCL) database is a common cause for these warnings.

Resolution

To complete the remediation, follow these sequential steps:

Identify the specific health failure: Navigate to the vSAN cluster > Monitor > vSAN > Skyline Health and identify which tests are failing.

1. Remediate the error or warning in vSAN health.

2. If it is just a warning, Silence the warring to allow for the cluster remediation to complete. Otherwise, fix the error on the vSAN host(s).

Note: It is not advisable to silence an error, this could lead to potential Data loss

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.