Troubleshooting Pipeline Access Errors in Aria Automation

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Failure to connect when trying to access the Pipelines section of the Aria Automation Portal
• You may see a 404 error. 
• You are unable to access the endpoints. 
• The appliance may respond to pings and remain accessible via SSH
• You see that services and pods are in the running state with no errors

Environment

Aria Automation 8.18.1

Cause

This can be caused by an ungraceful shutdown of Aria automation

Resolution

To restore the UI functionality, perform a graceful redeployment of the application services using the internal deployment script.

1. Prerequisites:

   • Ensure you have a recent snapshot of the Aria Automation appliance(s).
   • Obtain root credentials for the appliance(s).

2. Execute Graceful Redeploy:

   • Log in to the Aria Automation appliance as root via SSH.
   • Run the following command to stop existing service remnants

     /opt/scripts/deploy.sh --shutdown

   • Restart the virtual appliance node from vCenter to ensure a clean OS state.
   • Once the node is back online, execute the deployment script to initialize services:

     /opt/scripts/deploy.sh

   • Note: This process may take 15–30 minutes depending on environment performance. Monitor the output until it confirms the deployment is complete.

3. Verification:

   • Verify pod status using:

     kubectl get pods -n prelude

   • Confirm all pods are in a Running or Completed state.
   • Attempt to access the Pipelines after logging in to the Aria UI.