VMware

vCloud Director 5.1.3 Release Notes

vCloud Director 5.1.3 | 16 JAN 2014 | Build 1489357

Last updated: 13 FEB 2014

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Increased database support: vCloud Director has added support for the following databases.
    • Microsoft SQL Server 2008 R2 with service pack 1
    • Microsoft SQL Server 2008 R2 with service pack 2
    • Microsoft SQL Server 2012 with service pack 1
  • Increased guest operating system support: vCloud Director has added support for the following guest operating systems.
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows 8.1
    • SUSE Linux Enterprise Server 11 with service pack 3
    • Red Hat Enterprise Linux 6.4
    • Red Hat Enterprise Linux 5.9
  • Updated Java Runtime Environment version: vCloud Director 5.1.3 uses Java Runtime Environment 1.6.0 update 51.
  • Full-4 configuration for edge gateways: Full-4 provides the same increased capacity, performance, and security functions as Full configurations, but with 4 vCPUs. You can upgrade Full edge gateways to Full-4. Compact gateways must be upgraded to Full configuration before upgrading to Full-4. Full-4 edge gateways require vCloud Networking and Security 5.1.2c or later.

System Requirements and Installation

For information about system requirements and installation instructions, see the VMware vCloud Director Installation and Upgrade Guide.

Documentation

To access the full set of vCloud Director 5.1.3 documentation, go to the vCloud Director Documentation page.

Resolved Issues

This release resolves issues in the following areas.

General Issues

  • vCloud Director now supports Red Hat Enterprise Linux 6.4 and Red Hat Enterprise Linux 5.9
    vCloud Director has increased its support to include Red Hat Enterprise Linux 6.4 and Red Hat Enterprise Linux 5.9

  • vCloud Director sent alert emails for the datastores that were not managed by it
    vCloud Director sometimes sent email alerts about exceeding datastore threshold limits for datastores that are not managed by vCloud Director. This issue is resolved in vCloud Director 5.1.3.

  • Changing LDAP server moved imported LDAP users to Lost & Found
    After you changed the LDAP server configured for an organization, LDAP users in that organization were moved to Lost & Found on the next sync and had to be imported manually. This issue is resolved in vCloud Director 5.1.3.

  • Large numbers of thumbnail image requests could cause ESXi disconnects and system hangs
    When thumbnail image requests were enabled in vCloud Director, the ESXi hosts providing the thumbnail images could hang and become disconnected from vCloud Director when servicing large numbers of thumbnail requests. This issue is resolved in vCloud Director 5.1.3.

  • Trying to share items in a SAML/federation environment failed
    In a federated vCloud Director environment using SAML authentication, trying to share items failed. This issue is resolved in vCloud Director 5.1.3.

  • Storage used by virtual machine snapshots were not reflected in Chargeback Manager reports
    When you created a virtual machine snapshot in vCloud Director, the storage used by the snapshot was not reflected on chargeback reports. This occurred because Chargeback Manager was looking for events of the type com/vmware/vcloud/event/vm/modify while vCloud Director was generating events of the type com/vmware/vcloud/event/vm/modify_request. This issue is resolved in vCloud Director 5.1.3.

  • Quiescing a cell did not prevent new tasks from starting
    When you used the cell management tool to quiesce a cell, the cell still accepted tasks, preventing a graceful shutdown. This issue is resolved in vCloud Director 5.1.3.

  • Trying to access vCloud Director using Google Chrome failed with a Javascript error
    When you tried to access vCloud Director using Google Chrome, the operation failed with a Javascript error. This issue is resolved in vCloud Director 5.1.3.

  • No log entry to monitor automatic LDAP sync
    Logs did not contain any entry to specify the period of time it took for LDAP syncs to complete. This issue is resolved in vCloud Director 5.1.3.

  • Connecting to cells sometimes failed
    Trying to connect to vCloud Director cells sometimes failed with a 403 Forbidden error. This issue is resolved in vCloud Director 5.1.3.

  • vCenter Server sometimes disconnected from vCloud Director
    In some cases, vCenter Server occasionally disconnected from vCloud Director due to a database deadlock. This issue is resolved in vCloud Director 5.1.3.

Installation and Upgrade Issues

  • Kerberos authentication failed after upgrading vCloud Director
    After upgrading vCloud Director from version 5.1.0 to 5.1.2, Kerberos authentication failed. This issue is resolved in vCloud Director 5.1.3.

  • Incorrect virtual machine external IP addresses were displayed in the vCloud Director web interface after upgrade
    After upgrading vCloud Director to version 5.1.2, the vCloud Director web interface displayed incorrect external IP addresses for virtual machines. This issue is resolved in vCloud Director 5.1.3.

  • After upgrading to vCloud Director 5.1, expired items could not be deleted
    After an upgrade to vCloud Director 5.1, expired items were shown as suspended items and could not be deleted. If you attempted to manually delete the items, or if the containing organization had a policy of deleting expired items, an error of the following form was logged.

    Failed to purge object "vApp_system_20" as its dependencies cannot be purged.
    com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Failed to purge object "item_name" as its dependencies cannot be purged.

    This issue is resolved in vCloud Director 5.1.3.

  • After upgrading from vCloud Director 1.5.x, virtual machine network interfaces were changed
    After upgrading vCloud Director 1.5.x to 5.1.1, the network adapter types in your virtual machines could be changed in ways that caused network interfaces to be configured with incompatible network adapter type for a guest OS. Any virtual machine whose network adapter type was incompatible with its guest OS lost network connectivity after the upgrade. This issue was documented in Knowledge Base article 2047922 and is resolved in vCloud Director 5.1.3.

  • vCloud Director did not display external IP addresses for new virtual machines on the VMs list page
    After upgrading to vCloud Director 5.1.2, vCloud Director did not display external IP addresses for any new virtual machines created after the upgrade on the VMs list page. This issue has been resolved in vCloud Director 5.1.3.

  • Database script error during upgrade
    Trying to upgrade vCloud Director to version 5.1 sometimes failed with an error of the type:

    Unable to upgrade the database: java.sql.SQLException: Invalid object name 'dbo.hextoraw'.

    This issue is resolved in vCloud Director 5.1.3.

  • Slow database with high CPU usage after upgrade
    After upgrading to vCloud Director 5.1.2, the vCloud Director database was slow to respond and CPU usage was high. vCloud Director 5.1.3 resolves this issue by adding new indexes to improve database performance.

  • Error that shadow virtual machines had been duplicated after upgrading
    After upgrading vCloud Director, vCloud Director displayed a warning that shadow virtual machines had been duplicated, and all shadow virtual machines present before the upgrade said they had duplicates. This issue is resolved in vCloud Director 5.1.3.

Networking Issues

  • Gateways that failed during creation were allowed to redeploy
    When a gateway that failed during creation is redeployed, it leaves the gateway in an inconsistent state, which can cause problems if you upgrade to a new version of vCloud Director. vCloud Director 5.1.3 does not allow gateways that failed during creation to redeploy.

  • Adding or removing an IP address in the Sub-Allocate IP Pools dialog for an IP pool that was already in use caused the default gateway to be lost and broke the data path
    The vCloud Director web client sometimes allowed you to remove an External IP range that was in use. When this happened, you saw an error of the following form in the vCloud Director logs.

    ERROR | LocalTaskScheduler-Pool-4 | TaskServiceImpl
    | Unable to execute task NETWORK_GATEWAY_UPDATE_PROPERTIES(com.vmware.vcloud.entity.task:22e6eb93-bff1-4b14-b4f7-c2279dc81635)
    | vcd=084fcde4-a4ea-4918-a947-64008239a655,task=22e6eb93-bff1-4b14-b4f7-c2279dc81635
    com.vmware.vcloud.api.presentation.service.BadRequestException: Cannot update edge gateway "itprovider vshield"
    The following IP addresses are already being used: /nnn.nnn.nnn.nnn.

    This issue is resolved in vCloud Director 5.1.3.

  • Virtual machine list page displayed an error when a virtual machine's NIC was set to none n/w
    When a virtual machine's NIC was set to none n/w, the virtual machine list page displayed the error Unable to find network "null." This issue is resolved in vCloud Director 5.1.3.

  • VIM backing information was not displayed for vApp networks backed by VXLAN network pools
    The vCloud Director web client did not display VIM backing information for vApp networks backed by VXLAN network pools. This issue is resolved in vCloud Director 5.1.3.

  • Virtual machines using DHCP sometimes displayed IPv6 link local IP addresses
    The vCloud Director web client sometimes displayed IPv6 link local IP addresses for virtual machines using DHCP. vCloud Director 5.1.3 displays IPv4 addresses for all virtual machines with valid IPv4 addresses. For virtual machines without valid IPv4 addresses, vCloud Director 5.1.3 displays IPv6 non-link local IP addresses.

  • Unused organization VDC network incorrectly marked as in use and could be deleted
    Internal failures during vApp network creation could result in stale database entries that make an organization VDC network appear to be in use even though all resources using it had been deleted, disconnected, or moved. This issue is resolved in vCloud Director 5.1.3.

  • Gateway service changes did not trigger notifications
    When you made changes to gateway services, vCloud Director's notification system did not send notifications. This issue has been resolved in vCloud Director 5.1.3.

  • Task response XML when updating gateway services did not include owner information
    When you updated a gateway's services, owner information for the task did not appear in the organization's task list. This issue is resolved in vCloud Director 5.1.3.

  • Upgrading a gateway from compact to full configuration did not upgrade memory and CPU reservations
    When you upgraded a gateway from compact to full configuration, the operation did not upgrade memory or CPU to reflect the new gateway configuration. This issue is resolved in vCloud Director 5.1.3.

  • Redeploying a full-configured gateway in vCloud Director caused the gateway to appear as compact in vShield Manager
    When you used vCloud Director to redeploy a gateway with full configuration, the gateway appeared with compact configuration in vShield Manager. This issue is resolved in vCloud Director 5.1.3.

  • Gateways were sometimes deployed to datastores associated only with disabled storage profiles
    New gateways were sometimes deployed to datastores that were associated only with storage profiles that had been disabled. This issue is resolved in vCloud Director 5.1.3.

  • Firewall rules for a routed vApp network were removed when you modified the parent external network
    When you modified the parent external network of a routed vApp network, the vApp network's firewall rules were removed. This issue is resolved in vCloud Director 5.1.3.

  • vCloud Director displayed external IP addresses only for primary NICs
    When a virtual machine had multiple NICs, the vCloud Director web client displayed an external IP address only for the primary NIC. This issue is resolved in vCloud Director 5.1.3.

  • Network matching for routed vApp networks did not pick up matching parent network
    Routed vApp networks did not pick up the matching parent network during instantiation. When a routed vApp network was not matched, the network's firewall rules were lost. This issue is resolved in vCloud Director 5.1.3.

Virtual Machine and vApp Issues

  • Some items were not displayed in the drop-down menu when you right-clicked a virtual machine in a vApp diagram after a refresh
    When you right-clicked a virtual machine in a vApp diagram after refreshing the vApp diagram, some items were missing from the drop-down menu. This issue is resolved in vCloud Director 5.1.3.

  • Powering on multiple virtual machines in a vApp simultaneously sometimes failed
    When a vApp was powered on, but all virtual machines in the vApp were powered off or suspended, trying to power on multiple virtual machines in the vApp simultaneously failed. This issue is resolved in vCloud Director 5.1.3.

  • vApp creation could fail on a heavily loaded system
    When the system was operating under heavy load, new vApp creation could fail consistently with the error:

    Could not find object with moref "vm-xxxx" and VC ID "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx" in inventory category "VirtualMachine".

    This issue is resolved in vCloud Director 5.1.3.

  • vApp deployment or undeployment could fail with databse error
    In certain circumstances, when you tried to deploy or undeploy a vApp, the operation could fail with a database error of the following form.

    Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1
    org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1 at org.hibernate.jdbc.Expectations$BasicExpectation.checkBatched(Expectations.java:85)

    This issue is resolved in vCloud Director 5.1.3.

  • Guest customizations were not applied on Red Hat Enterprise Linux 6.x
    On virtual machines running Red Hat Enterprise Linux 6.x, guest customizations were not applied when Network Manager was running in the guest operating system. This issue is resolved in vCloud Director 5.1.3.

  • Administrators without administrator control rights could not view vApp networks of vApps they didn't own
    Administrators who did not have administrator control rights could not view vApp networks on vApps they didn't own. vCloud Director 5.1.3 resolves this issue.

  • Trying to create a vApp failed when vCenter Server took longer than 60 seconds to respond to the operation
    When vCenter Server was under a heavy load and took longer than 60 seconds to respond, trying to create a vApp in vCloud Director failed with an error of the type:

    Could not find object with moref "vm-xxxx" and VC ID "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx" in inventory category "VirtualMachine"

    This issue has been resolved in vCloud Director 5.1.3.

  • Trying to upload a Windows 8 virtual machine failed
    When you tried to upload a Windows 8 virtual machine, the operation failed because vCloud Director did not support the default NIC type used by Windows 8 virtual machines. This issue is resolved in vCloud Director 5.1.3.

  • Virtual machine operating system's default gateway was always assigned from the first IP pool in an external network with multiple IP pools
    For external networks with multiple IP pools, a virtual machine operating system's gateway was always assigned from the first IP pool listed for the external network. This occurred even when the first listed IP pool was disabled. In vCloud Director 5.1.3, a virtual machine is assigned its gateway IP address from the IP same pool that the machine gets its IP address from.

  • Changing virtual machine properties triggered unnecessary guest customization and changed the generated password
    When you changed the storage profile, metadata, or properties of a virtual machine, the automatically generated password for the virtual machine was changed and unnecessary guest customization was triggered. This issue is resolved in vCloud Director 5.1.3.

  • Trying to reduce the number of CPUs in a virtual machine failed when the virtual machine was configured with more CPUs than the ESX Server host
    When a virtual machine was configured with a greater number of CPUs than are present on the ESX host, trying to lower the number of CPUs on the virtual machine failed. This issue is resolved in vCloud Director 5.1.3.

  • Virtual machine password was changed in the vCloud Director web client but not applied to guest operating system after storage profile change
    After changing the storage profile of a virtual machine, the vCloud Director web client reflected a new automatically generated password for the virtual machine, but the password update was not applied to the guest operating system. This issue is resolved in vCloud Director 5.1.3.

  • You could set the number of virtual machines limit below the number of currently existing virtual machines
    vCloud Director allowed you to change the number of virtual machines limit to a value smaller than the number of virtual machines that already existed in vCloud Director. This issue is resolved in vCloud Director 5.1.3.

  • No way to limit the number of objects copied during shadow creation
    In previous versions of vCloud Director, there was no way to limit the number of objects copied during shadow creation. In vCloud Director 5.1.3, you can limit the number of objects copied to vCenter during virtual machine and vApp creation by adding the following parameters to the configuration table or global.properties.

    com.vmware.vcloud.fabric.storage.workQueueType=queueBehavior
    com.vmware.vcloud.fabric.storage.maxActivityThreads=M
    com.vmware.vcloud.fabric.storage.maxQueuedActivities=N
    fabric.storage.workQueueType=queueBehavior

    Set the values for M and N so that the combined value of M + N is more than the number parallel operations that you are performing.

vCloud API Issues

  • vCloud API requests to change the Limit of a StorageProfile to a lower value than is currently in use should have failed but did not
    Storage profile Limit values must be greater than or equal to the amount of storage already in use, however, API requests to reduce the Limit below what is already in use could complete without an error and actually reduce the Limit, which could cause consumers of that storage profile to fail in various ways. This issue is resolved in vCloud Director 5.1.3.

  • Guest customizations were not applied to vApps composed using the vCloud API
    When you created a vApp and applied guest customizations using the vCloud API, customizations other than the virtual machine name were not applied. This issue is resolved in vCloud Director 5.1.3.

  • Creating a vApp from a vApp Template using the vCloud API always assigned the default network adapter type
    When you created a vApp from a vApp Template with a network adapter type other than the default using the vCloud API and the composed input XML contained a Networkconnection section, the vApp was assigned the default network type. This issue is resolved in vCloud Director 5.1.3.

  • vCloud API displayed shared organization virtual datacenter networks that were inaccessible to the organization virtual datacenter
    When you queried organization virtual datacenter networks for an organization virtual datacenter using the vCloud API, the query returned a list of all shared organization virtual datacenter networks, even those that were inaccessible to the organization virtual datacenter. If you made the same query using the vCloud Director web client, only accessible networks were listed. In vCloud Director 5.1.3, the vCloud API query returns only accessible networks.

  • Guest operating system administrator password could not be retrieved using the vCloud API
    Using the vCloud API to get details for a vApp or vApp template did not return the guest operating system administrator password. This issue is resolved in vCloud Director 5.1.3.

Known Issues

The following issues are known to occur in this release of vCloud Director.

The known issues are grouped as follows:

General Issues

  • High CPU usage by the vCloud Director web interface
    When you run the vCloud Director web interface continuously for periods of a day or longer, the associated Flash process can use high levels of CPU.

    Workaround: Close and re-start the vCloud Director web interface.

  • HTTP ERROR 500 sometimes occurs when connecting to vCloud Director
    When you try to connect to vCloud Director using the web user interface or API, the error HTTP ERROR 500 sometimes appears.

    Workaround: Add the following to global.properties.

    cache.tenantcache.maxElementsInMemory=<numberOfOrgs x 5>
    // The value has to be more than the number of orgs CU may have/create before their next maintenance cycle (or) upgrade (or) cell-restart.

    cache.tenantcache.timeToIdleSeconds=10800000 //125 days
    cache.tenantcache.timeToLiveSeconds=10800000 //125 days
    // The above value means that CU may hit the issue again after 125 days. CU can increase the value according to their maintenance cycle (or) next upgrade (or) cell-restart.

  • Adobe Flex customizations are not applied when you use a different version of Adobe Flex than vCloud Director uses
    When you upload an Adobe Flex customization that is created using a version of Flex other than the one used by vCloud Director, the customization is not applied correctly.

    Workaround: For customizations for vCloud Director 5.1.3, use the Adobe Flex version 4.1.0.16076 SDK and compiler.

Installation and Upgrade Issues

  • Child resource pools sometimes aren't reconfigured after changing the elasticity of an allocation pool virtual datacenter and upgrading to vCloud Director 5.1.3
    When you change the elasticity of an allocation pool virtual datacenter, the elasticity of child resource pools is reconfigured when you power on vApps using those child resource pools. If you upgrade vCloud Director to version 5.1.3 after changing the elasticity of an allocation pool virtual datacenter but before powering on any vApps that use the affect child resource pools, the child resource pools are not reconfigured to reflect the new elasticity setting.

    Workaround:Cycle the elasticity of the virtual datacenter and power cycle a vApp that uses the affected child resource pool.

    1. Configure the virtual datacenter to use Elastic mode.
    2. Power off at least one vApp in all Allocation Pool organization virtual datacenters.
    3. Configure the virtual datacenter to use non-Elastic mode.
    4. Power on at least one vApp in all Allocation Pool organization virtual datacenters.
    5. Power the vApps back on.

  • Removing unused external IP addresses from sub-qllocated IP pools of the gateway fails after upgrading from vCloud Director 1.5.1
    After upgrading vCloud Director from version 1.5.1, attempting to remove unused external IP addresses from sub-allocated IP pools of a Gateway fails saying that IPs are in use.

    Workaround: If you are upgrading from vCloud Director 1.5.1, remove any unused external IP addresses from all Org Routed Networks before upgrading vCloud Director.

Localization Issues

  • Non-ASCII characters in VPN tunnel names appear as garbage characters in remote organizations
    When the name that you assign to a VPN tunnel includes non-ASCII characters, the non-ASCII characters in the name appear as garbage characters when you view the VPN tunnel from another organization. The VPN tunnel continues to function normally.

    Workaround: Do not use non-ASCII characters in VPN tunnel names.

  • Edge gateways cannot be created or updated with a pool server or virtual server that has non-ASCII characters in its name
    When you attempt to create an Edge gateway with a pool server or virtual server that has non-ASCII characters in its name, the operation fails. When you change the name of a pool server or virtual server to include non-ASCII characters, any Edge gateways associated with the pool server or virtual server cannot be updated.

    Workaround: Do not use non-ASCII characters in the names of pool servers or virtual servers that are used for Edge gateways.

  • A CD/DVD device name containing non-ASCII characters causes attempts to add the CD/DVD to a virtual machine to fail
    When you attempt to add a CD/DVD device with non-ASCII characters in its name to a virtual machine, the operation fails.

    Workaround: Change the CD/DVD device name to contain only ASCII characters before adding it to a virtual machine.

  • vApp template names cannot include only non-ASCII characters
    vCloud Director displays the error message "Invalid computer name: Computer name can only contain alphanumeric characters and hyphens, and must not contain only digits." if you use only non-ASCII characters in a vApp template name.

  • In languages other than English, object lists can be filtered only by columns that contain user-generated content
    When using vCloud Director in languages other than English, the filter function on object lists only works when filtering using columns that contain user-generated content, such as Name or vApp Name.

  • Host agent upgrade fails when the vCloud Director system name contains non-ASCII characters
    When you upgrade a vCloud Director system with non-ASCII characters in its name from version 5.1.x to version 5.1.3, the host agent fails to upgrade.

    Workaround: Perform an uninstall to remove the host agent, then prepare the host agent again.

  • Some localized messages display in English on Red Hat Enterprise Linux and CentOS 6.x
    On Red Hat Enterprise Linux and CentOS 6.x, some vCloud Director cells do not detect the correct locale at first start up or when the operating system is rebooted, which causes some messages to display in English.

    Workaround: Manually restart the cell using the command /opt/vmware/vcloud-director/bin/vmware-vcd restart.

Networking Issues

  • Trying to create an edge gateway with Full-4 configuration using vCloud Networking and Security 5.1.2a or earlier fails
    When you create an edge gateway, vCloud Director allows you to select Full-4 configuration for the gateway when you are using a version of vCloud parameters Networking and Security that doesn't support Full-4 configuration, but the create gateway operation fails.

    Workaround: Full-4 edge gateways require vCloud Networking and Security 5.1.2c or later.

Virtual Machine and vApp Issues

  • Removing the only hard disk from a powered-on virtual machine generates an error
    When you remove the only hard disk from a powered-on virtual machine, vCloud Director displays an error. Despite the error message, the disk is successfully removed.

  • Some networks are missing from the Select Organization VDC Network page of the new vApp wizard are disabled for vApp Authors

    When a vApp Author creates a new vApp network and selects Organization VDC Network in the new vApp network wizard, the number of networks displayed is off by the number of network that have already been added to the vApp. This may result in next page buttons being disabled since there are no more networks to be display in the list.

vCloud API Issues

  • API Backward Compatibility
    Incorrect DHCP information is returned in the DhcpService element when a vCloud API v1.5 client retrieves an OrgNetwork object from vCloud Director 5.1.

  • Control characters in an organization virtual datacenter name cause unmarshalling errors in vCloud Director SDKs and API
    Using the vCloud Director API or SDKs with an organization virtual datacenter that has control characters in its name, causes unmarshalling errors.

    Workaround: Do not use control characters in organization virtual datacenter names.

  • Allocation pool storage profiles do not work correctly after setting the capacity to unlimited using the vCloud Director API
    The vCloud Director mistakenly allows you to set the storage profile capacity on an allocation pool virtual datacenter to unlimited. After making this change, the storage profile cannot be updated using the vCloud Director web client.

    Workaround: Use the vCloud Director API to change the storage profile capacity to a value other than unlimited.