VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.6 Release Notes

VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.6\| 9 AUG 2024 \| Build 24171513 Check for additions and updates to these release notes.

VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.6| 9 AUG 2024 | Build 24171513

Check for additions and updates to these release notes.

Introduction to VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director

For information about the VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director interoperability with VMware Aria Automation Orchestrator, see the Product Interoperability Matrix.

Note:

Starting with version 8.12, the VMware vRealize Orchestrator name changes to VMware Aria Automation.

For information about installing and configuring the VMware Aria Automation Orchestrator plug-in for VMware Cloud Director 10.6, see the Using the VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director guide.

What's New

The VMware Aria Automation Orchestrator Plug-In for VMware Cloud Director 10.6 includes API changes ensuring the compatibility of the plug-in with version 10.6 of VMware Cloud Director.

API version compatibility with VMware Cloud Director

See VMware Product Interoperability Matrix for current information about API version compatibility with VMware Cloud Director.

Note: When managing multiple VMware Cloud Director instances running on different versions, you must create a connection to each of them separately and specify the API version that each version of VMware Cloud Director supports.

Download VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director

You can download VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.6 from the Broadcom Support Portal.

For more information about registering on the Broadcom Support Portal, see Register for an account on the Broadcom Support Portal and Communities. For product download instructions, see Download Broadcom products and software.

Earlier Releases of the VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director

Features and issues from earlier releases of the VMware Aria Automation Orchestrator plug-in for VMware Cloud Director are described in the release notes for each release. To review release notes for earlier releases of the VMware Aria Automation Orchestrator plug-in for VMware Cloud Director, see:

Resolved Issues

Running the relocateVM action from the VMware Aria Automation Orchestrator UI fails
When you run manually the relocateVM action from the VMware Aria Automation Orchestrator UI, the operation fails with the following exception.
```
error code = 405, minor error code = METHOD_NOT_ALLOWED
Server stack trace: com.vmware.vcloud.api.rest.toolkit.exceptions.MethodNotAllowedRestApiException: HTTP method not allowed
```
Resolution: Starting with VMware Cloud Director 10.6, to relocate a VM to a different storage profile, you must use the modifyVm PUT call. You can specify a storage profile by using VmType and making a modifyVm request. To accept the destination storage profile and run the PUT call, modify the existing relocate method in the VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director.

Note:
On the VMware Cloud Director side, a destination storage policy must be available on the VDC.

Known Issues

Workflows such as Composing a VApp or Power on a VApp fail with a jIOException accessible: module java.xml does not "opens com.sun.org.apache.xerces.internal.dom" to unnamed module error

The problem occurs because of the change of the Java Development Kit (JDK) version that VMware Aria Automation Orchestrator 8.17 and later use.

Workaround: See Broadcom knowledge base article 372509.
Running the Upload a vApp Template workflow fails

Starting with API version 32, uploading a vApp Template directly to a virtual data center (VDC) is not supported. The Upload a vApp Template workflow fails with a METHOD_NOT_ALLOWED error.

Workaround: To upload a vApp, run the Upload a vApp Template to Catalog workflow.
The Add a vApp with a New Virtual Machine workflow fails

Starting with API version 32, the Add a vApp with a New Virtual Machine workflow is not supported. When you attempt to run the workflow, it fails with a METHOD_NOT_ALLOWED error.

Workaround: None.
Running the Upload Media workflow fails if you choose not to upload the media file to a catalog

Starting with API version 32, uploading media directly to a virtual data center (VDC) is not supported. When you run the workflow, if you choose not to upload the media file to a catalog, the workflow fails.

Workaround: When you run the Upload Media workflow, select Upload to Catalog and select a catalog in which to upload the media file.