If you encounter a “402” error when accessing Aria Automation, the license assigned to your vRA instance has probably expired.
Attempting to do an inventory sync in VRLC will fail, too. If you look closely at the details of the error related to the failed inventory sync, you will see indications of an invalid license.
If that is your case, then the following steps can be used to resolve the issue:
Add a license to the vRLCM(Aria Suite Lifecycle) Locker
Logon to Aria Suite Lifecycle | Locker | License
Add License Manually
Once added, the license should appear with a Healthy Status.
Replace the license on the Aria Automation Instance
Login to Aria Suite Lifecycle | Lifecycle Operations
Go to Environments and locate the environment corresponding to your Aria Automation instance.
Click View Details
Click on the horizontal ellipses and click Add License.
The wizard should list the expired license.
Select the newly added license on the Select New License page and click Next.
On the Terminate License page, select the expired license and click Finish.
You should see the task complete sucessfully, on the Requests page.
You should now be able to log back into Aria Automation. However, if you get a “Bad Gateway” error, reattempt after a few minutes, as the pods might still be initializing.
SSH into the VRA node and run “kubectl get pods -n prelude” to check the status of the pods. In the screenshot, you can see that several pods have not been initialized yet. You can run a Linux watch on the command to monitor its output.
Wait until all the pods are “running” before you reattempt. In the previous screenshot, note that some pods are still being initialized.
Once all the pods are running, here is how it should look.
Now that all the pods are running, you should be able to log in to the Aria Automation console again.
Comments