Aria Automation 404 page not found - vco container is not starting

Products

• VMware Aria Suite

Issue/Introduction

• In Aria Automation, after a network disruption, the UI shows 404 page not found. 
• The Kubernetes pod for vco-app-<ID> shows a STATUS of 'CrashLoopBackOff'.  
• To confirm this, run the following command on the appliance:
       kubectl -n prelude get pods
• The status of the vco-app pod is CrashLoopBackOff
• Deploy.sh fails with an error starting pods. 

Environment

Aria Automation 8.x

Cause

A network disruption at the environment will cause service isolation, which might result in service / pod CrashLoopBackOff

Resolution

Shut down Automation services and reboot the appliance before starting the services again:

1. Log into one appliance via SSH or console as root
2. Shutdown Automation Services by running:
        /opt/scripts/deploy.sh --shutdown
3. Wait for the script to finish
   running 'kubectl -n prelude -get pods' should not show any running pods
4. Reboot the appliance(s)
5. Open the remote Console to the Automation appliance in vCenter and wait for the blue Login screen to available on all Automation appliances.
6. Login to one appliance via the Console or SSH as root
7. Start the Automation services by running:
        /opt/scripts/deploy.sh

8. Wait for the deploy.sh script to finish successfully. 

Additional Information

• For a clustered deployment, the deploy.sh --shutdown only needs to be performed on 1 out of the 3 nodes.