Unable to update DEM and DEO components fails while upgrading from vRA 7.2.x to 7.3.x

Products

VMware Aria Suite

Issue/Introduction

Symptoms:

After upgrading from vRealize Automation 7.2.x to 7.3.x, DEM and DEO components installed on custom path, such as D: drive, are not updated.
In the /usr/lib/vcac/tools/upgrade/upgrade.log file, you see entries similar to:

[UTC: 2017-05-24 18:19:41.105749; Local: 2017-05-24 18:19:41.105756] [INFO]: Upgrading dem components for node xxxxxxxxx

[UTC: 2017-05-24 18:20:24.865583; Local: 2017-05-24 18:20:24.865591] [INFO]: Command execution result:

Command id: xxxxxxxxxxxxxxxx

Type: upgrade-dem

Node id: xxxxxxxxxxxxxxx

Node host: xxxxxxxxxxxxxxx

Result:

Error installing DEM [xxxxxxxxx-dem-worker]

Error installing DEM [xxxxxxxxx-dem-worker]

Error: {u'1': [{u'resultMsg': u'Error installing DEM [xxxxxxxxx-dem-worker]', u'resultDescr': u''}, {u'resultMsg': u'Error installing DEM [xxxxxxxxx-dem-worker]', u'resultDescr': u'VMware.IaaS.Upgrade.Common.UpgradeFailedException: Error installing DEM [xxxxxxxxx-dem-worker]\r\n at VMware.IaaS.Upgrade.Common.DemUpgrade.UpgradeDem(DemInstallSettings dem, String installerDownloadFile, NotifyUserEventHandler notifyUserEvent, NotifyDebuggerEventHandler notifyDebuggerEvent, NotifyInstallationFailedEventHandler notifyInstallationFailedEvent)\r\n at VMware.IaaS.Upgrade.Common.DemUpgrade.Upgrade(DemUpgradeParameters parameters, NotifyUserEventHandler notifyUserEvent, NotifyDebuggerEventHandler notifyDebuggerEvent, NotifyInstallationFailedEventHandler notifyInstallationFailedEvent)\r\n at VMware.IaaS.Management.Commands.Upgrade.UpgradeDemCommand.Execute(IExecutionContext context, IList`1 parameters)'}]}

Status: FAILED

[UTC: 2017-05-24 18:20:24.874556; Local: 2017-05-24 18:20:24.874563]

[ERROR]: Failed to execute command upgrade-dem on node <HOSTNAME>

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vRealize Automation 7.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation 7.3.x
VMware vRealize Automation 7.4.x
VMware vRealize Automation 6.x
VMware vRealize Automation 7.1.x
VMware vRealize Automation Desktop 6.2
VMware vRealize Automation Desktop 6.2.x
VMware vRealize Automation 6.2
VMware vRealize Automation 7.0.x
VMware vRealize Automation 7.2.x

Cause

This issue occurs because while upgrading vRealize Automation to vRealize Automation 7.3 through the vRA VAMI, the IaaS DEMs and/or DEOs are installed on a custom install path.

For example, DEM and DEO components are installed on a drive other than C: drive.

Resolution

This is a known issue affecting VMware vRealize Automation 7.3.0.

This issue is resolved in VMware vRealize Automation 7.3.1 and VMware vRealize Automation 7.4, available at VMware Downloads.

Workaround:

To work around this issue vRealize Automation 7.3.0, perform these steps on each IaaS node that has DEM/DEO installed on a non-default location:

Revert the IaaS node to a snapshot taken before the DEM/DEO upgrade failure.
Log in to the node and open a Web browser.
Enter the URL for the Windows installer download page.

For example, https://vcac-va-hostname.domain.name:5480/installer.

where vcac-va-hostname.domain.name is the name of the primary (master) vRealize Automation appliance node.
Click the IaaS installer link.
When prompted, save the installer file, [email protected].

Note: Do not change the file name. It is used to connect the installation to the vRealize Automation appliance.
Right-click on the [email protected] setup file and click Run as administrator.
Complete the wizard to upgrade all IaaS components on this node.