VMware vRealize Orchestrator Plug-In for vCloud Director 10.0.0.1 | 9 April 2020 | Build 15966366

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to the VMware vRealize Orchestrator Plug-In for vCloud Director 10.0.0.1

The VMware vRealize Orchestrator plug-in for vCloud Director 10.0.0.1 release runs on VMware vRealize Orchestrator 8.0, 7.6 and 7.5. For information about installing and configuring the vRealize Orchestrator plug-in for vCloud Director 10.0.0.1, see the Using VMware vRealize Orchestrator Plug-Ins guide. 

What's New in the vRealize Orchestrator Plug-In for vCloud Director 10.0.0.1

The vRealize Orchestrator Plug-In for vCloud Director 10.0.0.1 provides bug fixes.

Due to changes in vRealize Orchestrator 8.0 and later versions, when you run workflows that involve uploading or downloading vApp templates and media files, you must provide upload and download file paths under the /usr/lib/vco directory. In the vRealize Orchestrator Appliance server host, this file path maps to the /data/vco/usr/lib/vco directory.

API version compatibility with vCloud Director Director

API version vCloud Director version 
33.0 10.0
32.0 9.7
31.0 9.5
30.0 9.1
29.0 9.0

Note: When managing multiple vCloud 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.

 

Earlier Releases of the vRealize Orchestrator Plug-In for vCloud Director

Features and issues from earlier releases of the vRealize Orchestrator plug-in for vCloud Director are described in the release notes for each release. To review release notes for earlier releases of the vRealize Orchestrator plug-in for vCloud Director, click one of the following links:

Resolved Issues

  • Running workflows that call the getHosts() action fails

    Running workflows that call the getHosts() action from custom scripts fails with VCloudPluginException messages.

  • Running the Update a gateway workflow clears the load balancing settings of the edge gateway

    Running the Update a gateway workflow results in clearing the load balancing settings of the edge gateway.

  • If the name of a virtual machine contains spaces, querying the virtual machine by its name fails

    If the name of a virtual machine contains spaces, querying the virtual machine by its name fails. The following exception messages appear in the client log and in the integration-server.log files: Illegal character in query.

  • Running the Download a vApp template workflow results in downloading an invalid VMDK file

    Running the Download a vApp template workflow results in downloading an invalid VMDK file. This happens because the OVF descriptor file is downloaded two times - as an OVF descriptor file and as a VMDK file. Despite having different names, both files have the same size.

     

Known Issues

  • In vRealize Orchestrator 8.0.1, some input text boxes of the Add a vApp Network workflow do not load

    In vRealize Orchestrator 8.0.1, some input text boxes of the Add a vApp Network workflow do not load. In the UI, you see the following error: Some data cannot be retrieved. If the problem persists, contact your system administrator. Running the workflow results in a Gateway - This field is required error.

    Workaround: None.

  • 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 plugin-in to version 10

    Existing workflow actions fail after upgrading the vRealize Orchestrator plugin-in to version 10.0, because of the integration with the latest API schema.

    Workaround: Perform one of the following procedures.

  • Running some sample workflows in the vRealize Orchestrator Client fails due to missing input parameters text boxes

    Some input parameters text boxes in sample vCloud Director workflows, such as Add Catalog Item, Update Catalog Item, and Add a Connection, are not displayed in the HTML5-based vRealize Orchestrator Client. Attempting to run these workflows results in errors.

    Workaround: Use the Java-based Orchestrator Legacy Client.

check-circle-line exclamation-circle-line close-line
Scroll to top icon