Aria Automation services fail to start or IP changes fail after HCX migration
search cancel

Aria Automation services fail to start or IP changes fail after HCX migration

book

Article ID: 447218

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Introduction

Aria Automation, Identity Manager (vIDM), or Suite Lifecycle nodes migrated to a new network/vCenter using HCX may fail to start services or prevent IP address modifications. This occurs because vApp options are not preserved during HCX migration.

Symptoms

  • vIDM or Aria Automation services fail to start after migration.
  • Unable to change the IP address of the appliance following standard procedures.
  • Error: The vApp configuration for the appliance is not available in vCenter.
  • The /opt/vmware/etc/vami/ovfEnv.xml file is missing or lacks network configuration.

Environment

  • VMware Cloud Foundation (VCF)
  • VMware Aria Automation 8.x
  • VMware Aria Suite Lifecycle Manager (LCM)
  • VMware Aria Identity Manager (vIDM) 3.3.x
  • VMware HCX

Cause

HCX migration (Bulk, vMotion, or RAV) does not support the migration of vApp configurations/options for VMware software appliances. When these appliances are moved to a new vCenter, the network metadata required for service initialization is lost.

Resolution

To manually restore services on existing versions, perform these steps in the specific order of LCM -> vIDM -> vRA:

  1. Ensure each node is reachable via ping or SSH before proceeding to the next node.
  2. Add the vApp Options to the Aria Suite Lifecycle (LCM) appliance in vCenter. Start the appliance and verify the UI is accessible. Confirm settings in /opt/vmware/etc/vami/ovfEnv.xml.
  3. Add the vApp Options to the Identity Manager (vIDM) appliance in vCenter.
  4. Update the vIDM database with the new IP address using steps in .
  5. Restart the horizon-workspace service and verify the /etc/hosts file contains the correct master IP.
  6. Add the vApp Options to the Aria Automation (vRA) appliance in vCenter.
  7. Verify host, DNS, and NTP settings in /opt/vmware/etc/vami/ovfEnv.xml.
  8. Monitor pod startup using the following command: kubectl get pods -A -w

For defects and enhancements, subscribe to this article (reference: ) to be updated on fix status.

Additional Information

Powered by Wolken Software