In Aria Automation deploy.sh script, the csp_update_non_default_orgs function fails with "curl: (22) The requested URL returned error: 502"

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• The /opt/scripts/deploy.sh output (also stored in /var/log/deploy.log) shows that system startup fails in the section "Populating initial identity-service data"
• Under csp_update_non_default_orgs , we see the following error:
  • curl: (22) The requested URL returned error: 502
• The identity service log /services-logs/prelude/identity-service-app/file-logs/identity-service-app.log shows the following errors:
  • Error: com.vmware.identity.exception.BadGatewayException: REST error received:
  • {"errors":[{"code":"internal.server.error","message":"Internal Server Error","parameters":null}]}, status code: 500 INTERNAL_SERVER_ERROR
• Re-trusting Identity Manager and Re-registering the Automation host with Identity Manager in Aria Lifecycle do not resolve the issue

Environment

• VMware Aria Automation 8.x
• VMware Aria Lifecycle 8.x
• VMware Identity Manager 3.3.7

Cause

• Gateway (LB) communication issue on the Identity Manager side

Resolution

1. Open globalenvironment (the vIDM Environment) in LCM
2. In the options, choose to Re-Trust Load Balancer
3. Run /opt/scripts/deploy.sh once more

Note: Load balancer communication issues may also occur if the vIDM appliance is not updated with the correct DNS server. Refer to the "Change DNS settings on a vIDM appliance" KB to update the vIDM appliance with the correct DNS IP.