vRealize Automation 7 – Error – Unable to get metadata

So today my heart sunk when I tried to log into the vRA 7 IaaS portal and was presented with this lovely message:

vra_error1

Now, I had just recently attempted an upgrade of vRA 7.0.1 to 7.1 and failed miserably (more on that in a later post) so I had to roll back all of my changes (reverting snapshots, etc.) and brought all the services back. All seemed fine until I tried to log into the IaaS portal.

One of the first things I checked was the services registration on the vRA VAMI interface (Services tab). I thought perhaps the order of events of the rollback had skewed something. I observed the following:

vra_error3

So clearly something was afoot. I did a little digging and came across the following KB article:

Logging in to tenant fails after adding authenticated proxy config in VAMI in VMware vRealize Automation 7.0.x (2144067)

The interesting thing here, is that just a few hours before, I added a proxy server to the VAMI configuration in order to get the updates I needed from https://vapp-updates.vmware.com. As per the KB article I inspected the following log file:

After sifting through the log for about 10 seconds I saw this:

Then as per the KB article I edited the following config file:

Edit /etc/sysconfig/proxy

Modify the following line to include the hostname of the VRA appliance (I did the hostname, FQDN and the shared cluster hostname just to be sure). I have modified the actual names for the purpose of this post. “localhost” and “127.0.0.1” were already present.

I then restarted the vRA services:

As per instruction, I waited 5 minutes and sure enough all was working again.

vra_error4

This is one of those really silly problems which really, should not exist. What is more interesting is that the KB article states that this is related to an authenticated proxy for the appliance update downloads. I have not configured authentication for my proxy so it seems it affects regardless of how it is configured.

If someone can shed some light on why this is actually a problem, one that VMware can’t seem to solve then please let me know.

Leave a Reply

Your email address will not be published. Required fields are marked *