Interoperability Configuration for Aria Automation Orchestrator and vCD during Multi-Stage TCP Upgrades
search cancel

Interoperability Configuration for Aria Automation Orchestrator and vCD during Multi-Stage TCP Upgrades

book

Article ID: 427088

calendar_today

Updated On:

Products

VMware Telco Cloud Infrastructure VMware Telco Cloud Platform VMware Cloud Director VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

This article outlines configuration requirements and known issues identified during interoperability testing of the VMware Aria Automation Orchestrator plugin 10.6.0 with VMware Cloud Director (VCD) 10.4.3 and VMware Aria Automation Orchestrator 8.18.1.

Important: This configuration is documented specifically for transitional states within a multi-stage upgrade path. It is applicable when the environment must temporarily operate in this version combination to facilitate a sequential upgrade to a final, aligned VMware Telco Cloud Platform (TCP) Solution.

Administrators operating in this transient phase may encounter the following error patterns:

  • Connection Failure: java.lang.AssertionError: Workflow execution is in unexpected state! Error in logging in with user administrator to the vCloud host
  • Workflow Execution Error: TypeError: Cannot find function updateInternalState followed by Caused by: com.thoughtworks.xstream.converters.ConversionException: No converter available
  • Inventory Traversal Error: java.lang.NullPointerException at internal.helpers.VroHelpers.removeSiteInfoFromName
  • VM Operation Failure: Unable to relocate VM - The operation is not supported on the object

Environment

 

  • vRO Plug-in for vCD 10.6.0

  • vRO / vRealize Orchestrator 8.18.1 

  • vCD 10.4.3

  • TCP Multi-Stage Upgrade Paths

 

Cause

These issues stem from distinct interoperability conflicts between the Orchestrator 8.18.1 runtime and the VCD 10.4.3 API:

  1. AssertionError: The connection workflow defaults to an unspecified or incompatible API version.

  2. ConversionException: The Orchestrator 8.18.1 runtime includes updated XStream libraries that lack specific converters used by the plugin.

  3. NullPointerException: The VCD host connection was configured using a specific Cell FQDN rather than the public Load Balancer URL, causing path parsing failures.

  4. Relocate VM Error: This is a hard product limitation for this specific version combination.

Resolution

To ensure stability during this transition phase, apply the following configurations:

  1. Configure API Version When executing the "Add a connection" workflow in the Orchestrator UI, explicitly set the API version to 37.3. Do not rely on auto-negotiation.
  2. Update Connection Topology Ensure the VCD host is registered using the Public Load Balancer URL.
    • Correct: https://<public-lb-fqdn>/
    • Incorrect: https://<specific-cell-fqdn>/
  3. Apply Serialization Fix If the ConversionException or updateInternalState errors persist, apply the workaround steps detailed in KB 372509 to address the XStream converter gap in the Orchestrator runtime.



Additional Information

Relocate VM Limitation: The error "The operation is not supported on the object" during VM relocation is expected behavior for this version pair. No workaround exists; avoid this operation while in this transitional state.

Powered by Wolken Software