Search the VMware Knowledge Base (KB)
View by Article ID

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

  • 0 Ratings

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 xxxxxxxxx.state.mo.us

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


 

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

To resolve this issue, perform these steps on each IaaS node that has DEM/DEO installed on a non-default location:
 
  1. Revert the IaaS node to a snapshot taken before the DEM/DEO upgrade failure.
  2. Log in to the node and open a Web browser.
  3. 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.

  4. Click the IaaS installer link.
  5. When prompted, save the installer file, setup__vcac-va-hostname.domain.name@5480.exe.

    Note: Do not change the file name. It is used to connect the installation to the vRealize Automation appliance.

  6. Right-click on the setup__vrealize-automation-appliance-FQDN@5480.exe setup file and click Run as administrator.
  7. Complete the wizard to upgrade all IaaS components on this node.

Tags

vRA, vRealize Automation, DEM, DEO, Upgrade

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: