The VCF Identity Broker (vIDB) component reports a Disconnected status within Fleet Management following the patch

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• After performing a patch on vIDB component the password status (vmware-system-user) shows as "Disconnected" within VCF Operations UI >> Fleet Management >> Passwords >> VCF Management.
  
  
  
  
• The "/var/log/vrlcm/vmware_vrlcm.log" reports below error stating "Failed to fetchVMSP config details from VMSP"
  

  ERROR vrlcm[1235] [pool-3-thread-80] [c.v.v.l.u.SshUtils]  -- Exception cause : com.jcraft.jsch.JSchException: Auth fail for methods 'publickey,password,keyboard-interactive'
  ERROR vrlcm[1235] [pool-3-thread-80] [c.v.v.l.u.SshUtils]  -- JSchException encountered
  ERROR vrlcm[1235] [pool-3-thread-80] [c.v.v.l.v.p.t.FetchInfraDetailsFromVMSPClusterTask]  -- Failed to fetchVMSP config details from VMSP clsuterCaused by: java.lang.RuntimeException: Cannot create session for ssh://vmware-system-user@<VIDB-IP>

Environment

VCF Operations 9.x
VCF Identity Broker 9.x
VCF Fleet Management 9.x

Cause

This is a known cosmetic issue within the VCF Fleet Management Passwords UI infrastructure.

Resolution

Broadcom is aware of the behavior. A permanent fix is expected to be included in a future release of VCF Operations.

Workaround

In order to restore the healthy state of vIDB user vmware-system-user, follow the manual synchronization steps:

Resetting the vmware-system-user password for VCF Identity Broker

Additional Information

The "Remediate Password" option updates the VCF Locker but does not synchronize with the Kubernetes Secrets where the actual vIDB credentials reside. 
If the user remediates the password from VCF Fleet, the subsequent patch will utilize the Kubernetes Secret, causing nodes to show disconnected with VCF Fleet Password UI following the upgrade/patch.