Updating to vRA 7.3.1/7.4 fails when IaaS installation binaries were not updated to new version

Products

• VMware Aria Suite

Issue/Introduction

This article provides information on what steps to take when there is a failover of the vRA virtual appliances and the replica nodes still have the old IaaS installation files.

Symptoms:

• When you perform an automatic upgrade to vRealize Automation 7.3.1/7.4, the upgrade fails on the primary IaaS website node.
• In the Management Agent log file, you see entries similar to:
  
  error MSB4057: The target "UpgradeApprovalsEntitlements" does not exist in the project.
  
  Note: The Management Agent MSI upgrade log could be found in the following location: %Installation_folder%\VMware\vCAC\Management Agent\Logs\All.log

Environment

VMware vRealize Automation 7.3.x
VMware vRealize Automation 7.4.x

Cause

This issue occurs when:

• The current Primary appliance is not the first VAMI url listed in the affected Management Agent's configuration (VMware.IaaS.Management.Agent.exe.Config) file, in section <managementEndpoints>.
• The Replica virtual appliance(s) failed to upgrade automatically and the automatic IaaS upgrade started.

Resolution

This is a known issue affecting VMware vRealize Automation 7.3.x.

Currently, there is no resolution.

Workaround:
To work around this issue, follow either one of the workarounds:

1. Restore the environment to the backup taken before upgrade.
2. Change the current Primary appliance to be the same as the first VAMI url listed in the affected Management Agent's configuration (VMware.IaaS.Management.Agent.exe.Config) file, in section <managementEndpoints>.
3. Retry the upgrade.

Alternatively:

1. Copy the contents of the IaaS download directory from the Primary appliance  in /opt/vmware/share/htdocs/service/iaas/download.
2. Overwrite with it the contents of the same folder on all replicas respectively. This way only the IaaS nodes (including the IaaS database, if it is external) should be reverted to pre-upgrade state and its upgrade could be retriggered by running the automatic IaaS upgrade script manually ("/usr/lib/vcac/tools/upgrade/upgrade").