Retention of no longer relevant vCLS Degraded health warning entry in vSphere cluster services-- health history of vCenter UI.

Products

• VMware vCenter Server

Issue/Introduction

To provide details on when and when not to disregard a "Degraded" warning entry under vSphere cluster services-Health History section.

Symptoms:
A "Degraded" warning entry under the Health History section for Cluster - Monitor - vSphere Cluster Services will display in the vCenter GUI.


However, steps have already been carried out to restore the cluster Health:

1) Putting a Cluster in Retreat Mode


2) "vSphere DRS functionality was impacted due to unhealthy state vSphere Cluster Services", vCLS virtual machines are not getting deployed after VCSA upgrade to 7.0 (318191)
Ref  KB: https://knowledge.broadcom.com/external/article/318191/vsphere-drs-functionality-was-impacted-d.html

The object id example: vCLS-5eb1ede1-dc71-4609-b5d6-475fea072f7a belongs to a vcls vm that is no longer in existence on the cluster and so is a historical entry.

Environment

VMware vCenter Server 7.0.3

Cause

vCenter does not automatically clear historical entries from this section of the UI.

There could be multiple scenarios that result in this warning message being displayed, 

Some example causes are including but not limited to:

A user has powered off or deleted vCLS VMs from a DRS enabled cluster.
When vCLS is disabled on a cluster using Retreat Mode.
vCLS VMs are recreated by vCLS service.

Resolution

The idea of having that history is for awareness in case the issue is frequently occurring and we will not be able to clear it manually.

Additional Information

What we see in vSphere cluster services-- health history is just the historical data, this is the history status and status will reflect as degraded since the vCLS VM's will shut down and will be completely removed. This is an expected behavior.

As long as the current Cluster Service Status is Healthy, the history can be ignored and has no functional impact on the vCenter server.

The idea of having that history is for awareness in case the issue is frequently occurring and we will not be able to clear it manually.