VMware

VMware vCenter Orchestrator Plug-In for vCenter Server 5.0.1.1 Release Notes

VMware vCenter Orchestrator Plug-In for vCenter Server 5.0.1.1 | 13 Jun 2012 | Build 232

VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581

VMware vCenter Orchestrator 4.2 | 24 Aug 2011 | Build 5277

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 vCenter Orchestrator Plug-In for vCenter Server 5.0.1.1

The vCenter Orchestrator Plug-In for vCenter Server 5.0 runs on VMware vCenter Orchestrator 4.1.x and VMware vCenter Orchestrator 4.2.x. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCenter Server 5.0.x.

What's New in This Release

Version 5.0.1.1 of the plug-in addresses a number of issues. To upgrade the plug-in, you must install version 5.0.1.1 on your existing installation. You can download version 5.0.1.1 from the VMware vCenter Orchestrator Plug-In for vCenter Server download page.

Resolved Issues

The following issues are resolved in this release:

  • Register virtual machine workflow cannot register templates
    This issue is resolved in this release. Now you can register templates by using the Register virtual machine workflow.
  • The Add CD-ROM workflow fails when you try to map to an ISO image from your datastore
    This issue is resolved in this release. The workflow does not fail when you select a datastore ISO file as a deviceType.
  • Some obsolete parameters are removed from the Set virtual machine performance workflow
    Obsolete parameters related to the virtual machine network settings are removed from the Set virtual machine performance workflow, because these parameters are not supported by the ESX/ESXi hosts. The removed parameters are:
    • setNetwork
    • netAverageBps
    • netBurstSize
    • netPeakBps
    • netShapeEnabled
    To set the network shaping parameters for a virtual switch on an ESX/ESXi host, you can use the Update standard virtual switch or Update port group in standard virtual switch workflow.
  • Property or method vm not found on object VcClusterAntiAffinityRuleSpec
    Suppose you assign a value to the vm property of a VcClusterAffinityRuleSpec or a VcClusterAntyAffinityRuleSpec object in a scriptable task of the workflow that you design. When you run the workflow, it fails with the following error message: Property or method 'vm' not found on object VcClusterAntiAffinityRuleSpec.

    This issue is resolved in this release.

  • Domain account is always mandatory in Clone, Windows with single NIC workflow
    This issue is resolved in this release. In the Clone, Windows with single NIC workflow, the domain account is mandatory only when you want to join a domain.
  • Windows customization workflows fail if you do not specify a pool, and the host is not in a cluster, even though pool is optional
    In the Windows customization library workflows, when you specify a host, the pool input is optional. This works properly only if the host is in a cluster. If the host is a standalone host, the workflow fails with the following error message:
    Task 'CloneVM_Task' error: A specified parameter was not correct.
    spec.location.pool (Dynamic Script Module name : vim3WaitTaskEnd#20)

    This issue is resolved in this release.

  • The Attach host system to distributed virtual switch workflow fails when you do not pass the uplinkPortgroup parameter
    The uplinkPortgroup parameter is not mandatory, but when you do not enter a value, the workflow fails with the following error message: TypeError: Cannot read property "key" from null (Workflow:Attach host system to distributed virtual switch / Attach host system (item0)#10).

    This issue is resolved in this release.

  • When you try to activate the FDM/HA host failover feature and add a host from a cluster in a workflow, the workflow fails
    When you try to activate the FDM/HA host failover feature and add a host from a cluster, the workflow fails with the following error message in vCenter Server: A specified parameter is not correct. In the log files, the hostarray parameter does not contain any value.

    This issue is resolved in this release.

  • vCenter Server task trigger cannot be activated
    If you run a workflow that contains a vCenter Server trigger and you use the Inventory Service, the trigger cannot be activated and the workflow remains in suspended mode.

    This issue is resolved in this release.

  • You cannot use the scripting API to refresh the information about a distributed virtual switch port from VLAN
    vCenter Server provides no task for refreshing of distributed virtual switch port by using the Orchestrator scripting API.

    This issue is resolved in this release.

  • Integration problems of plug-in with vCenter Inventory Service
    This release resolves an issue in the integration with vCenter Inventory Service. The issue leads to a Bad request error in the logs. The performance is also improved.

Top of Page

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator Plug-In for vCenter Server 5.0 release:

  • When you install the vCenter Server 5.0.1.1 plug-in, the vCenter Server 4.1 plug-in is not removed from your system
    When you install the vCenter Server 5.0 plug-in, the vCenter Server 4.1 plug-in installation is not removed. Having both versions of the plug-in might cause some issues.
    Workaround: Remove the vCenter Server 4.1 plug-in before installing the vCenter Server 5.0 plug-in. To uninstall the plug-in:
    1. Log in as an administrator to the machine on which the Orchestrator server is installed.
    2. Navigate to the vCenter Server 4.1 plug-in .dar file.
      • If you installed Orchestrator with the vCenter Server installer, the default path is:
        install_directory\VMware\Insfrastructure\Orchestrator\app-server\server\vmo\plugins\o11nplugin-vsphere41.dar.
      • If you installed the standalone version of Orchestrator, the default path is:
        install_directory\VMware\Orchestrator\app-server\server\vmo\plugins.
    3. Restart the vCenter Orchestrator configuration service and the vCenter Orchestrator server.
  • Stopping the vCenter Inventory Service causes an error in the plug-in
    If you stop the vCenter Inventory Service on a vCenter Server instance that is registered with the plug-in, the Inventory view of the plug-in in the Orchestrator client displays an error message.
    Note: If you start the vCenter Inventory Service again, you can refresh the Inventory view of the plug-in in the Orchestrator client to use the plug-in with enabled vCenter Inventory Service.

    Workaround: Restart the Orchestrator service to use the plug-in with disabled vCenter Inventory Service.

  • Certificates required for vCenter Server instances in a linked mode group
    If you register a vCenter Server instance that is in a linked mode group, you must import the certificates of all vCenter Sever instances that you added to the configuration in this operation, so that Orchestrator can recognize all vCenter Server instances in the linked mode group.
  • The vCenter Server 5.0.1.1 plug-in might run out of memory
    The vCenter Server 5.0 plug-in might run out of memory with an OutOfMemory error message when you configure it to work with vCenter Orchestrator 4.1.

    Workaround: Modify the jetty-service.conf file on the machine on which the Orchestrator server and the vCenter Server 5.0 plug-in are installed.

    1. Log in as an administrator to the machine on which the Orchestrator server and the vCenter Server 5.0 plug-in are installed.
    2. Locate the jetty-service.conf file.
      The default location is: C:\Program Files\VMware\Infrastructure\Orchestrator\configuration\jetty\jetty-service.conf.
    3. Open the file in a text editor.
    4. Add the following line:
      wrapper.java.additional.7=-XX:MaxPermSize=128m
    5. Change wrapper.java.maxmemory=64 to wrapper.java.maxmemory=256.
    6. Save and close the file.

    Top of Page