/var/log/vmware/wcp/wcpsvc.log, you may find entries similar to:Supervisor control plane failed: No connectivity to API Master: connectivity , config status REMOVINGFailed to get EAM agencies. Err ServerFaultCode: EAM is still loading from database. Please try again later.Failed to list EAMAgent. Err ServerFaultCode: EAM is still loading from database. Please try again later.
/var/log/vmware/eam/eam.log, you may find entries similar to:| WARN | vim-async-0 | ExtensionSessionRenewer.java | 227 | [Retry:Login:com.vmware.vim.eam:a6307ae03f141f9d] Re-login failed, due to:com.vmware.eam.security.NotAuthenticated: Failed to authenticate extension com.vmware.vim.eam to vCenter.
Caused by: com.vmware.vim.binding.vim.fault.InvalidLogin: Cannot complete login due to an incorrect user name or password.
| ERROR | vim-monitor | VcListener.java | 124 | An unexpected error in the changes polling loopcom.vmware.eam.EamRemoteSystemException: Unexpected error communicating with the vCenter server.
VMware vCenter Server
WCP is dependent on EAM service for various operations including deletion of supervisor cluster. This issue occurs when the EAM service is not able to authenticate to vCenter due to a discrepancy between the "vpxd-extension" certificate stored in VECS and the certificate information stored in the vCenter Server Database for the EAM extension.
Update the certificate of the EAM extension in VPXD using the below procedure:
vCert - expired certificate replacement script
# unzip -q vCert-6.0.1-20250516.zip# cd vCert-6.0.1-20250516# chmod +x vCert.py# ./vCert.py
option 3: Manage certificatesoption 6:vCenter Extension thumbprintsExample:
For this specific issue, EAM service will report as MISMATCH
Note: There may be other extensions such as image builder and rbd reporting mismatch
Note: All the extensions which are reported as MISMATCH are updated and the respective services will be restarted
Example output:
option 6:vCenter Extension thumbprints to verify if the extensions are updated