VCF SSO component configuration status reverts to "Not Configured" daily in VCF Operations 9.0.2

Products

• VCF Operations

Issue/Introduction

• In VMware Cloud Foundation (VCF) Operations, the VCF Single Sign-On (SSO) component configuration status persistently reverts to "Not Configured" within the VCF Operations UI.
• Manually selecting and configuring the component successfully updates the UI status to "Configured"; however, this state is temporary. After approximately 24 hours, the status reverts to "Not Configured" and remains in that state until manual intervention occurs.
• Despite the VCF Operations UI status reflecting "Not Configured," the backend VCF SSO integration remains actively functional on the individual components, and SSO authentication directly to the components succeeds without interruption.
• The /storage/log/vcops/log/vcops-bridge.log contains the following entries indicating the scheduled deletion of the authsource:
  YYYY-MM-DDTHH:MM:SS INFO  vcfops-bridge 6744 [ops@4413 threadId="324" threadName="DistTaskAuthSourceTaskTimer"] [com.vmware.vcops.bridge.server.vidb.api.impl.DeleteInactiveAuthSourceAPI.deleteInactiveAuthSource] - Resource is not active 03###############################cd
YYYY-MM-DDTHH:MM:SS WARN  vcfops-bridge 6744 [ops@4413 threadId="324" threadName="DistTaskAuthSourceTaskTimer"] [com.vmware.vcops.bridge.server.vidb.api.impl.DeleteInactiveAuthSourceAPI.delete] - Deleting auth source with componentId 03###############################cd

Environment

VMware Cloud Foundation Operations 9.0.2

Cause

The vCenter Server GUID is formatted in uppercase characters. A scheduled background cleanup job executes to remove authsource entries from the Operations Database for components that no longer exist. This validation routine utilizes a case-sensitive GUID comparison to match the resource. Due to the uppercase GUID in the Resources table, the case-sensitive comparison fails, resulting in the unintended deletion of the component entry.

Resolution

This is a known cosmetic issue affecting VCF Operations 9.0.2. Broadcom Engineering is aware of the issue, and a permanent fix will be included in a future release.