Upgrading vRA 7.x might fails with error: Management Agent automatic upgrade failed

Error in VAMI:

 

Error in updatecli.log:

 

The Management Agent registers the IaaS Windows server with the vRealize Automation appliance, automates the installation and management of IaaS components, and collects support and telemetry information. The Management Agent runs as a Windows service.

 

If there is communication issue between management agent and vRA appliance the upgrade might fail with the error mentioned above.

  • You can check Last Connected time in vRA VAMI -> vRA Settings -> Cluster – if this is in hours / days then there is something wrong with management agent communication with vRA appliance.
  • In my experience when I check the All.log of management agent C:\Program Files (x86)\VMware\vCAC\Management Agent\Logs, I found below error (management agent having incorrect vRA appliance name)

 

[UTC:2018-05-02 05:34:20 Local:2018-05-02 01:34:20] [Trace]: [sub-thread-Id=”5″  context=””  token=””] Task Ping is executing…
[UTC:2018-05-02 05:34:21 Local:2018-05-02 01:34:21] [VMware.Cafe]: [sub-thread-Id=”5″  context=””  token=””] (33440) PUT config/nodes/4B8CAFA0-953D-43B8-8FE2-99CA5328F8EA/ping
[UTC:2018-05-02 05:34:21 Local:2018-05-02 01:34:21] [VMware.Cafe]: [sub-thread-Id=”5″  context=””  token=””] (33440) Request Exception, retrying: System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: The remote name could not be resolved: ‘<vRA_FQDN>’

 

Resolution:

Quick fix if you want to continue with automatic upgrade, uninstall and re-install management agent with correct vRA appliance name. Perform the upgrade again.

(OR)

The other option is to perform manual upgrade of IaaS Components, follow the below steps (This also includes uninstalling and re-installing the management agent)

After upgrading only appliance you would see this message:

 

  • Uninstalled and re-installed proxy agent and rebooted IaaS service.

 

 

You can monitor the IaaS Upgrade progress in vRA VAMI:

 

We are done 🙂

 

Leave a Reply

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