VMware

vCloud Director 5.1.2 Release Notes

vCloud Director 5.1.2 | 25 APR 2013 | Build 1068441

Last updated: 25 APR 2013

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Rights for creating, reverting, and removing snapshots: Rights for creating, reverting, and removing snapshots have been added, allowing system administrators to configure these rights for all roles.
  • Allocation pool organization virtual datacenters can be elastic or non-elastic: Starting with vCloud Director 5.1.2, system administrators can configure Allocation Pool organization virtual datacenters with Single Cluster Allocation Pool (SCAP), making them non-elastic. This is a global setting that affects all Allocation Pool organization virtual datacenters. By default, Allocation Pool organization virtual datacenters have Single Cluster Allocation Pool enabled. Systems upgraded from vCloud Director 5.1 that have Allocation Pool organization virtual dataceters with virtual machines spanning multiple resource pools have Single Cluster Allocation Pool disabled by default.

    To change the Single Cluster Allocation Pool setting go to System > Administration > General > Miscellaneous. Before enabling Single Cluster Allocation Pool, migrate any virtual machines on secondary resource pools to the organization virtual datacenter's primary resource pool.

  • vCloud Director is now supported on Red Hat Enterprise Linux 6.3
  • Support for Microsoft SQL Server 2012: vCloud Director now supports Microsoft SQL Server 2012 databases.
  • Additional guest operating system customization support: vCloud Director now supports customization of the following guest operating systems:
    • Microsoft Windows Server 2012

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.2 documentation, go to the vCloud Director Documentation page.

Resolved Isues

This release resolves issues in the following areas.

General Issues

Oracle (Sun) Java Runtime Environment updated to version 1.6.0_37
Oracle Java Runtime Environment (JRE) has been updated to version 1.6.0_37, which addresses multiple security issues. Oracle has documented the CVE identifiers that are addressed in JRE 1.6.0_37 in the Oracle Java SE Critical Patch Update Advisory for October 2012.

Installation and Upgrade Issues

Upgrade error: ORA-00001: unique constraint (VCLOUD.IP_RANGE_UNIQUE) violated
Fixed a problem that could cause upgrade to vCloud Director 5.1 to fail with the following error: ORA-00001: unique constraint (VCLOUD.IP_RANGE_UNIQUE) violated.

Upgrade error: Unable to upgrade the database: java.sql.SQLException: Violation of UNIQUE KEY constraint 'uq_os_name_version_update'
Fixed a problem that could cause upgrade to vCloud Director 5.1 to fail with the following error: Unable to upgrade the database: java.sql.SQLException: Violation of UNIQUE KEY constraint 'uq_os_name_version_update'. Cannot insert duplicate key in object 'dbo.os'.

Upgrade error: ORA-00001: unique constraint (VCD.UQ_TR_RESOURCE) violated
Fixed a problem that could cause upgrade to vCloud Director 5.1 to fail with the following error: ORA-00001: unique constraint (VCD.UQ_TR_RESOURCE) violated.

Upgrade error: java.sql.SQLException: The INSERT statement conflicted with the FOREIGN KEY constraint
Fixed a problem that could cause upgrade to vCloud Director 5.1 to fail with the following error: java.sql.SQLException: The INSERT statement conflicted with the FOREIGN KEY constraint "fk_roleright_to_role".

Upgrade error: Unable to upgrade the database: java.sql.DataTruncation: Data truncation
Fixed a problem that could cause upgrading to vCloud Director 5.1 to fail with the following error: Unable to upgrade the database: java.sql.DataTruncation: Data truncation.

Upgrade error: Unable to upgrade the database: java.sql.SQLException: Cannot insert the value NULL into column
Fixed a problem that could cause upgrade to vCloud Director 5.1 to fail with the following error when one or more virtual machines in the system being upgraded were in an invalid state: Unable to upgrade the database: java.sql.SQLException: Cannot insert the value NULL into column 'memory_configured_mb', table 'vcloud01.dbo.computevm'; column does not allow nulls. INSERT fails.

vCenter Server sometimes disconnects from vCloud Director after upgrading to vCloud Director 5.1
Fixed a problem that could cause vCenter Server to sometimes disconnect from vCloud Director after you upgrade vCloud Director.

Networking Issues

Attempting to change the IP range of an external network fails
Fixed a problem that causes attempting to expand or shrink the IP range of any external network with its entire IP range sub-allocated to a gateway fails.

Peer network displays an incorrect size
Fixed a problem that could cause a peer network configured with a size of 32 during VPN tunnel creation to appear with a size of 31.

Uknown error when viewing or modifying network pool properties
Fixed a problem that could cause an unknown error when you attempt to view or modify the properties of a network pool backed by vSphere port groups.

VLAN ID in use error
Fixed a problem that could cause creating two external networks using the same VLAN ID to fail with the following error message: Failed to create external network as port group name or its VLAN ID id is in use.

Virtual Machine and vApp Issues

Deploying a vApp from a public catalog sometimes fails
Fixed a problem that caused deploying a vApp from a public catalog to fail if the catalog has an organization virtual datacenter network with the same name as an organization virtual datacenter network on the organization you attempted to deploy the vApp to.

Error adding a virtual machine or vApp: ORA-00001: unique constraint (VCLOUD.IX_NETWORKINTERFACE) violated
Fixed a problem that could cause an upgraded vCloud Director 5.1 installation to fail when you attempt to add a vApp or virtual machine with an internal server error and display the following error: ORA-00001: unique constraint (VCLOUD.IX_NETWORKINTERFACE) violated.

Virtual machine NICs assinged IP addresses that are not in range
Fixed a problem that allowed a virtual machine NIC configured with manual IP mode to be assigned an IP address using the REST API that was not in range and switched NICs configured in this way to DHCP IP mode.

Empty storage profile menu
Fixed a problem that could cause the Storage Profile drop-down menu to appear empty while trying to instantiate a vApp from a public catalog.

Attempting to change a vApp computer name fails
Fixed a problem that could cause attempting to change a vApp's computer name to fail.

Virtual machine deployment fails on organization virtual datacenters spanning more than one cluster
Fixed a problem that causes shadow virtual machine and vShield Edge virtual machine deployment to fail on organization virtual datacenters spanning more than one cluster after you upgrade from vCloud Director 1.5 to 5.1.

Virtual machine SID does not persist when you add a vApp to a catalog
Fixed a problem that could cause a virtual machine's change SID option not to persist when adding the vApp to a catalog.

Virtual Machine IP assignment changes when converting a vApp to a vApp template
Fixed a problem that could cause a virtual machine's IP assignment mode to change from Static IP Pool to DHCP when you convert the vApp to a vApp template with the option Customize VM settings.

Direct organization virtual datacenter networks can use IP addresses only from a primary subnet
Fixed a problem in the vCloud Director web client that limits direct organization virtual datacenter networks to see IPs only from one subnet even if the external network has more than one subnet. With vCloud Director 5.1.2, a direct organization virtual datacenter network can give a virtual machine a manual IP address from any of the subnets assigned to the external network.

Correct Network Matching When Instantiating a vApp Template Into an Organization
Fixed a problem that could cause network matching to fail when instantiating a vApp template into a different organization.

Attempting to power on a virtual machine fails with a no suitable resources error
Fixed a problem that could cause adding a new virtual machine to a vApp to fail with the following error: The operation failed because no suitable resource was found.

Provider virtual datacenter is full
Fixed a problem that could cause powering on virtual machines on some provider virtual datacenters to fail with an error stating that the provider virtual datacenter is full.

Attempting to delete a hard disk from a fast-provisioned virtual machine fails
Fixed a problem that could cause attempting to delete a hard disk from a fast-provisioned virtual machine to fail.

Virtual machine console displays a black screen
Fixed a problem that could cause opening a virtual machine console to become indefinitely stuck in a connecting state.

Guest operating system customization fails during Sysprep
Fixed a problem that caused guest operating system customization to fail during Sysprep on Windows Vista and later.

vCloud API Issues

REST API returns duplicate references to the same vApp
Fixed a problem that caused the REST API to return duplicate references to a vApp that was created by and later shared to the same user.

Known Issues

The following known issues have been discovered through rigorous testing and will help you understand some behavior you might encounter in this release.

Unused external IP addresses from sub-allocated IP pools of the gateway fail after upgrading From vCloud Director 1.5.1 to vCloud Director 5.1.2
After you upgrade vCloud Director from version 1.5.1 to version 5.1.2, 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 Organization Routed Networks before you upgrade vCloud Director.

Reconfigure Edge Gateways and vApp networks after you upgrade from vCloud Director 1.5.x to vCloud Director 5.x
After upgrading vCloud Director from 1.5.x to 5.x, you must reconfigure Edge Gateways and vApp networks, as described in Reconfigure Edge Gateways and vApp Networks to Enable Normal Operation. An additional reconfigure step might be necessary to remove hidden firewall rules that were put in place before the firewall rules were converted to the new format. These rules might block traffic that should not be blocked.

To remove these rules, follow the procedures in Reconfigure Edge Gateways and vApp Networks to Enable Normal Operation and then, after all steps in those procedures are complete for Edge Gateways and vApp networks, update the firewall configurations of any affected Edge Gateways or vApp networks. Any change to the firewall configuration will remove these hidden rules. For example, enable firewall rule logging, commit the change, then disable firewall rule logging and commit the change.

Highlighting the shared tunnel key during VPN tunnel creation causes key characters to disappear
When you type a shared key during VPN tunnel creation and then highlight the shared key, the last several characters of the key disappear.

Workaround: Do not highlight the shared key using your mouse. Instead, select the text by pressing ctrl + A.

vApp template IP mode changes when you add the template to My Cloud or start and cancel the New vApp Network wizard
When you add a vApp template to My Cloud and select None in the NIC's network drop-down menu or start and cancel the New vApp Network wizard, a NIC configured with DHCP IP mode changes to Static-IP Pool.

Attempting to download a vApp template from a catalog or opening the download manager redirects the browser
When you attempt to download a vApp template from a catalog or click Download Manager, your browser is redirected to http://www.oracle.com/technetwork/. This is caused by an out-of-date version of Java Runtime Environment.

Workaround: Upgrade to the latest version of Java Runtime Environment.

Virtual machine network stops working after upgrading from vCloud Director 1.5.x
In some cases, virtual machine networks become nonfunctional after you upgrade from vCloud Director 1.5.x. This loss of functionality is the result of a mismatch between virtual machine NIC configuration and the virtual machine's guest operating system.

Workaround: Delete the virtual machine's NIC and a new virtual machine NIC type that supports the virtual machine's guest operating system. See Choosing a network adapter for your virtual machine.

  1. Power off the virtual machine.
  2. In the vCloud Director client, click My Cloud
  3. In the left pane, click VMs.
  4. Right-click the virtual machine and select Properties.
  5. Click the Hardware tab and click Delete in the NICs section.
  6. Click Add.
  7. (Optional) Modify the NIC settings.
  8. Click OK.

Outdated NAT rule displayed after deleting a virtual machine with a NAT rule
After powering off and deleting a virtual machine with a NAT rule from a powered on vApp that is configured with a fenced or routed vApp network, an outdated NAT rule is displayed on the Networking tab for the vApp.

Workaround: Refresh the configure networking list, then view configure services again.

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.