no Healthy upstreamidentity-service-app pod in Aria Automation appliance fails to resolve or establish connectivity with the VMware Identity Manager (vIDM) appliance.identity-service-app pods cannot initialize.To resolve this issue, you must restore the health and connectivity of the upstream VMware Identity Manager cluster.
Verify the status of your pods to confirm if the identity-service-app is failing to initialize. You can monitor the pod initialization by running the following command:
watch kubectl get pods -n prelude
If the identity-service-app pods are failing to initialize, investigate your VMware Identity Manager (vIDM) cluster for health issues or offline nodes.
Work with your identity team or support to resolve the underlying vIDM cluster errors.
Bring at least one node in the vIDM cluster back online. Once a singular vIDM node is healthy and reachable, the identity-service-app pods will successfully initialize.
Shut down services by running:
If necessary, after restoring vIDM health, restart the vRA services with an /opt/scripts/deploy.sh command. If this still fails, perform a graceful reboot of the VMware Aria Automation system to restart the services:
deploy.sh --shutdown
Power cycle the appliance VM in vCenter.
Restart the services by running:
deploy.sh
Once the pods fully initialize, the VMware Aria Automation UI will load successfully.