VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.5.1.1| 17 MAY 2024 | Build 23733211 Check for additions and updates to these release notes. |
VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.5.1.1| 17 MAY 2024 | Build 23733211 Check for additions and updates to these release notes. |
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.
Starting with version 8.12, the VMware vRealize Orchestrator name changes to VMware Aria Automation.
For information about installing and configuring the vRealize Orchestrator plug-in for VMware Cloud Director 10.5.1.1, see the Using the vRealize Orchestrator Plug-in for VMware Cloud Director guide.
The VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.5.1.1 provides bug fixes.
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.
You can download VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director 10.5.1.1 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.
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:
Running the Add an Organization workflow fails with a ConversionException
If you configure VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director with VMware Aria Automation Orchestrator 8.12 and later, the Add an Organization workflow fails because of incompatibility with VMware Aria Automation Orchestrator. The workflow fails with the following error.
com.thoughtworks.xstream.converters.ConversionException: No converter available
The Download a vApp workflow fails with a FileNotFoundException
and SSLHandshakeException
If you configure VMware Aria Automation Orchestrator Plug-in for VMware Cloud Director with VMware Aria Automation Orchestrator 8.12 and later, when you run the Download a vApp workflow, the selected vApp does not download at the given target location. The workflow fails with the following error.
Could not download:https://test.eng.vmware.com/transfer/test.ovf. javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
The issue is resolved in this release, however, you must enter /usr/lib/vco
as the download location for the VMware Aria Automation Orchestrator server.
Running the Add a Connection
workflow results in a the trustAnchors parameter must be non-empty
error message when using the plug-in with vRealize Orchestrator 8.9.1 and later
If you use the plug-in with vRealize Orchestrator 8.9.1 and later, an attempt to run the Add a Connection
workflow fails with an error message.
the trustAnchors parameter must be non-empty
The vco-server-app.log
log file displays an error.
java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
This happens because the vRealize Orchestrator plug-in for VMware Cloud Director utilizes the keystore of the local filesystem rather than the API offered by the plug-in SDK.
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.
Existing workflow actions fail after upgrading the vRealize Orchestrator plug-in to version 10.3.0.1a
Existing workflow actions fail after upgrading the vRealize Orchestrator plug-in to version 10.3.0.1.a, because of the integration with the latest API schema.
Workaround: Remove the action from the workflow and add the same action again, binding the parameters manually.