VMware

VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.2.3 Release Notes

VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.2.3 | 10 September 2015 | Build 3004239

VMware vRealize Orchestrator 6.0.0 (formerly vCenter Orchestrator) | 9 December 2014 | Build 2289455

VMware vRealize Orchestrator 6.0.1 (formerly vCenter Orchestrator) | 12 March 2015 | Build 2510740

VMware vRealize Orchestrator 6.0.2 (formerly vCenter Orchestrator) | 5 May 2015 | Build 2707386

VMware vRealize Orchestrator 6.0.3 (formerly vCenter Orchestrator) | 10 September 2015 | Build 3000579

VMware vRealize Automation 6.2 (formerly vCloud Automation Center) | 9 December 2014 | Build 2299574

VMware vRealize Automation 6.2.1 (formerly vCloud Automation Center) | 12 March 2015 | Build 2553372

VMware vRealize Automation 6.2.2 (formerly vCloud Automation Center) | 9 June 2015 | Build 2754336

VMware vRealize Automation 6.2.3 (formerly vCloud Automation Center) | 10 September 2015 | Build 3025163

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 VMware vCenter Orchestrator Plug-In for vCloud Automation Center

The VMware vCenter Orchestrator vCloud Automation Center plug-in provides access and control over any vCloud Automation Center or vRealize Automation system.

The vCenter Orchestrator vCloud Automation Center plug-in provides the following capabilities:

  • Interact with and manage catalog services, catalog items, advanced services custom resources, service blueprints and resource actions, tenants, approvals and entitlements, work items, and blueprints.
  • Allow organizations to automate operations on the vRealize Automation IaaS model entities.
  • Integrate your existing business logic and models with an arbitrary vRealize Automation server.
  • Add a vRealize Automation as a policy-based, declarative multi-hypervisor, provisioning functionality to an existing top level service catalog portal.
  • Use the vCloud Automation Center plug-in policies to place a workload when a scale out update is needed based on performance triggered by vRealize Operations.
  • Enable workflow designers to include create, read, update, and delete operations for an arbitrary vRealize Automation model entity in any entity set.
  • Connect dynamically to a vRealize Automation system and provision a virtual machine from a vRealize Automation blueprint.

The VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.2.3 release runs on VMware vRealize Orchestrator 6.0.0, 6.0.1, 6.0.2, and 6.0.3. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCloud Automation Center 6.2.

For information about vRealize Orchestrator, vRealize Orchestrator plug-ins, or vRealize Automation see the following documentation:

What's New in vCenter Orchestrator Plug-In for vCloud Automation Center 6.2.3

This release of the vCenter Orchestrator Plug-In for vCloud Automation Center introduces the following new functionality:

  • vCenter Orchestrator Plug-In for vCloud Automation Center 6.2.3 works with vRealize Automation 6.2, 6.2.1, 6.2.2, and 6.2.3 and vRealize Orchestrator 6.0.0, 6.0.1, 6.0.2, and 6.0.3.

Resolved Issues

The following issues are resolved in vCenter Orchestrator Plug-In for vCloud Automation Center release 6.2.3:

  • vRealize Orchestrator is unable to process special characters
    If you make a request that uses the method getBodyAsJson() of the scripting class vCACCAFEServiceResponse, and if the serviceResponse(the instance of this class) contains special characters, an error appears in the Orchestrator logs similar to SyntaxError: Unexpected token in object literal. In this example, literal applies to the a catalog item request where the request form description or approval response includes special characters. The plug-in now supports special characters. .

  • vRealize Orchestrator displays incomplete error message in the logs
    The error message 403 Forbidden is the only information that is displayed if a you performs an actions for which you does not have permission. The extended information exists, for example, User username@domain.name is not entitled to request this catalog item., but is not displayed. The plug-in now displays the entire message.

  • Error regarding Illegal instant due to time zone offset transition when running workflows after a spring daylight savings time transition
    The vRealize Automation database stores the date and time in UTC format, but the vRealize Automation plug-in treats the timestamp as local date and time. If you run a workflow or other event during the daylight savings time adjustment, workflows fail with a error similar to following for the Prague region:
    Caused by: java.lang.IllegalArgumentException: Cannot parse "2015-03-29T02:48:14": Illegal instant due to time zone offset transition (Europe/Prague)
    at org.joda.time.format.DateTimeParserBucket.computeMillis(DateTimeParserBucket.java:336)
    at org.joda.time.format.DateTimeFormatter.parseDateTime(DateTimeFormatter.java:672)


    You might also see this error if you are browsing the vCAC:VirtualMachines inventory in vRealize Orchestrator. The plug-in now processes the timestamp as UTC.

  • vRealize Orchestrator workflows fail on mapped IaaS machines if changes were made during daylight savings transition
    The vRealize Automation IaaS database stores the date and time in UTC format, but the vRealize Automation plug-in treats the timestamp as local date and time. If you run a workflow or other event during the daylight savings time adjustment, the timestamp is an incorrect value. The error in the Orchestrator logs is similar to Exception: Unable to execute 'fetchRelation' for type : virtualFolder_VirtualMachines : java.lang.IllegalArgumentException: Cannot parse "2015-03-08T02:31:02.037": Illegal instant due to time zone offset transition (America/New_York). The plug-in now processes the timestamp as UTC.

Known Issues

Some issues have been discovered and the following information is intended to help you understand behavior that you might encounter in this release:

  • Error when running the Import vCenter Virtual Machine workflow in vRealize Orchestrator
    When you run the Import vCenter Virtual Machine workflow provided by the plug-in, the workflow fails and an error similar to the following appears:
    Link collections can only contain Entity instances, current is: null (Dynamic Script Module name : updateEntity#12)
    The error occurs when the virtual machine storage path is associated with a single storage unit from a storage cluster, but the reservation is associated with the cluster.

    Workaround: Before you run the Import vCenter Virtual Machine workflow, you must configure the reservation compute resources with all the individual child storage units for the cluster.
    1. In vRealize Automation, select Infrastructure > Reservations.
    2. Select the vSphere reservation.
    3. Click the Resources tab.
    4. Select the cluster associated with the virtual machine that you will import in the Compute resources drop-down menu.
    5. Select and configure the child nodes in the Storage list.
    6. Click Save for each storage unit.
    7. Click Save on the page when all the child storage units configured.

  • Retrieving approval information by using a script results in missing property '@type' error
    The missing property type error is returned when you use the following script to retrieve approval information:
    var service = vcacHost.createApprovalClient().getApprovalApprovalInfoService();
    var approvalInfo = service.getApprovalInfo( approvalId );


    Workaround: Use the following script to retrieve approval information:
    var approvalClient = vcacHost.createApprovalClient();
    var vars = [ approvalId ]; var approvalInfo = approvalClient.getWithVariables("/info/approvals/{0}", vars);
    var approvalPolicy = new vCACCAFEApprovalDescriptiveReference() ;
    approvalPolicy.setId(approvalInfo.getProperty("policy").getProperty("id"));
    approvalPolicy.setName(approvalInfo.getProperty("policy").getProperty("name"));
    approvalPolicy.setDescription(approvalInfo.getProperty("policy").getProperty("description"));

  • On the Items tab of the vCloud Automation Center console, the name and description of some vCAC Infrastructure Administration resources do not display correctly
    If you publish a catalog item by using the Advanced Service Designer based on an infrastructure administration workflow that has an output parameter of vCAC:Entity type, when consumers request the catalog item successfully, the name and description of the provisioned items do not display correctly.

  • The requests workflows for waiting do not work correctly when a vCloud Automation Center host is added with Per User Session connection and the vRealize Orchestrator server is restarted during running of the workflows
    The Wait for work item, Wait for resource action request, and Wait for catalog item request workflows result in "Unable to retrieve authentication for this task" instead of "Approved" or "Rejected" if a vCloud Automation Center host is added with Per User Session connection and the vCenter Orchestrator server is restarted during running of these workflows.

  • vCloud Automation Center Plug-in API documentation is still in development
    vCAC and VCACCAFE modules of the vCenter Orchestrator API Explorer do not provide complete API documentation.

    Workaround: You can download the latest versions of the API documentation from vRealize Automation Documentation or access the vRealize Automation API documentation on https://vRealize_automation_appliance_host/component-registry/services/docs.

  • Searching for business groups returns results for all hosts
    When you run workflows for updating or deleting business groups, or adding, updating, or deleting custom properties for a business group from the Workflows view, there is no option to restrict the search function to a particular vCloud Automation Center host.

    Workaround: Run these workflows from the Inventory view.

    1. Click the Inventory view in the Orchestrator client.
    2. Right-click the business group you want to update.
    3. Select the workflow to run.

  • The workflows provided in the plug-in do not perform the same validation as vCloud Automation Center UI
    The vCloud Automation Center user interface performs validation checks, but not all of this logic is accounted for in the workflows provided with the plug-in. For example, vCloud Automation Center prevents you from creating a tenant with a non-unique URL, but the plug-in workflow does not validate this. Make sure that your custom workflows take care of any validation required by vCloud Automation Center.

  • The vCACCAFEAuthenticationGroupService.updateCustomGroup method removes all members of the updated group

    Workaround: Before using the vCACCAFEAuthenticationGroupService.updateCustomGroup method, retrieve the group members and reassign them to the group after the update, for example:

    // Create a vCACCAFEAuthenticationGroupService instance to perform operations, where host is the vcac host configured by the vcaccafe plug-in.

    var groupService = host.createAuthenticationClient().getAuthenticationGroupService();

    // Retrieve current members, where groupToBeUpdated is the target custom group

    var membersUsers = groupService.getUsersInGroup(tenant, groupToBeUpdated, criteria, pageable);

    var membersGroups = groupService.getGroupsByCriteriaAndDomainAndParentGroup(tenant, criteria, domain, groupToBeUpdated);

    // Update the group, retrieve the updated group, and reassign the members:

    groupService.updateCustomGroup(tenant, groupToBeUpdated);

    var updatedGroup= groupService.getGroup(tenant, groupToBeUpdated.getPrincipalId().asString());

    groupService.assignGroupsAndUsersToCustomGroup(tenant, updatedGroup, membersGroups, membersUsers);

Top of Page