vRA7.x services do not register after a restart (2147446)

最新推荐文章于 2022-04-07 11:03:11 发布

原创最新推荐文章于 2022-04-07 11:03:11 发布 · 52 阅读

0 ·

CC 4.0 BY-SA版权

本文介绍了解决vRealize Automation重启后出现的服务未正确注册问题的方法。通过重新输入SSO凭证并保存设置，等待一段时间后，所有服务将重新注册并恢复正常状态。

After restarting the vRealize Automation Appliance, you experience these symptoms:

In the vRealize Appliance’s VAMI page, located at https://<vRA_FQDN_or_IP>:5480 under the Services tab, many services are not REGISTERED, either showing no status or are showing as FAILED.
In the /var/log/vmware/vcac/catalina.out file, you see errors similar to:
vcac: [component="cafe:identity" priority="WARN" thread="tomcat-http--16" tenant context="abmDcLPx" token="a
bmDcLPx"] com.vmware.vcac.authentication.service.impl.AuthenticationMessageNotificationServiceImpl.loadServiceInfoAndRegisterSolutionUserForTenants:63 - No serviceInfo found for serviceInfoId [e5415d38-21a8-4948-9ea5-4ec968ab2e2c] of serviceType [com.vmware.csp.component.software.service]
org.springframework.security.authentication.BadCredentialsException: { "error": "invalid_client", "error_description": "Client is not found."

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Resolution

To resolve the issue:

Log in to vRealize Automation’s VAMI page configuration at https://vRA_FQDN_or_IP:5480 using root credentials.
Navigate to vRA Settings > SSO.
Re-enter SSO credentials by adding ‘administrator@vsphere.local’ as the user and the associated password.
Click the Save Settings button and wait for vRealize Automation to re-register to Horizon SSO.
Navigate to the Services > refresh to verify that all services are again REGISTERED.

NOTE: This may take approximately 10 minutes for services to fully report back and you may have to log out of the vRealize Automation VAMI and log back in.