Verifying the Status of VMware Aria Automation Pods to Resolve “Bad Gateway” Error

As you may have noticed, after starting the VMware Aria Automation appliance, the user interface displays an error message of “Bad Gateway” for a relatively long time, possibly due to the fact that the appliance is still in the startup phase (it takes a bit longer to come up). But how can we verify this?

Before attempting more invasive solutions, let’s first check if all the pods are in the “Running” state. To do this, execute the following command:

kubectl -n prelude get pods

After entering this command, check the “Status” column in the result to confirm that all pods are available. If any pod has a value of “READY” 0/1, it means that it is not yet ready.

Wait for all pods to have a value of “Ready” 1/1 or 2/2 before attempting to access the user interface again. As you can see from the images, the “Bad Gateway” message is related to some pods (in yellow) that are not yet available.

Attempting to access the user interface before all pods are ready may result in further errors or unexpected consequences. Therefore, it’s essential to wait until all pods are up and running before attempting to access the user interface.

To verify the status of the pods, you can execute the previous command again after waiting for a few minutes (perhaps even just ten). If all pods are now in the “Running” state, you should not encounter the “Bad Gateway” message anymore.

By following this simple verification process, we have avoided taking hasty decisions that might have led to unexpected consequences. So, take a deep breath, relax, and let the appliance complete its startup phase before attempting to access the user interface. Happy automating!