VMware

vCloud Director 1.5.1 Release Notes

vCloud Director 1.5.1 | 15 MAR 2012 | Build 622844

Last updated: 15 MAR 2012

What's in the Release Notes

The release notes cover the following topics:

What's New

New platform support
vCloud Director 1.5.1 adds support for the following:

  • vCenter Server 5.0 Update 1
  • ESXi 5.0 Update 1
  • vShield 5.0.1
  • Red Hat Enterprise Linux 5 (64 bit), Update 7 (as a supported vCloud Director Server operating system)

Firewall rules can be configured with CIDR blocks, IP ranges, and port ranges
vCloud Director 1.5.1 allows you to enter CIDR blocks and IP ranges for the source and destination when creating firewall rules using the UI or REST API. In addition, you can enter port ranges for the source and destination ports using the UI (but not the REST API). If you create a firewall rule that includes port ranges using the UI, you will not be able to query the rule using the REST API.

Added system notification for lost connection to AMQP host
If vCloud Director loses its connection to the AMQP host, vCD sends an email to the recipients specified in System Notification settings (Administration > System Settings > Email).

Enhanced cell management tool and log collection script
This release includes a new version of the cell management tool (cell-management-tool). With this version, you are not required to enter an administrator user name and password to access help and usage information. If a command requires a user name and password, the cell management tool prompts you to enter the information.

This release also includes a new version of the log collection script (vmware-vcd-support). With this version, you are not required to enter an administrator user name and password to use the script.

Support for AES-256 encryption for VPN tunnels
This release adds support for the AES-256 encryption protocol when creating a Site-to-Site VPN tunnel.

Increased the retention maximum for vCenter Chargeback history
In vCloud Director 1.5.1, the maximum possible setting for "Chargeback Event History to Keep", was increased from 365 days to 1096 days.

Resolved issues
This release delivers a number of bug fixes that have been documented in the Resolved Issues section.

System Requirements and Installation

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

The most current information about supported databases and supported versions of ESX/ESXi and vCenter Server is available from the VMware Product Interoperability Matrixes.

VMware vCenter Chargeback 1.6.2 and 2.0.x support vCloud Director 1.5.x, but do not support vCloud Director 1.0.x. If you are upgrading your environment, make sure you upgrade vCloud Director before you upgrade vCenter Chargeback. See the VMware vCenter Chargeback documentation for more information.

Upgrading to vCloud Director 1.5.1

If you are installing vCloud Director for the first time, follow the installation instructions in the VMware vCloud Director Installation and Configuration Guide.

vCloud Director software is distributed as a Linux executable file named vmware-vcloud-director-1.5.1-622844.bin. Running this file requires superuser (root) privileges.

The upgrade process is slightly different depending on whether your vCloud Director installation has one cloud cell or multiple cloud cells.

Upgrading a vCloud Director Installation with a Single Cloud Cell

This scenario describes how to upgrade a vCloud Director installation with a single cloud cell.

To upgrade a single cloud cell:

  1. Log in to the target server as root.
  2. Download the installation file to the target server.
  3. Ensure that the installation file is executable.
    The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following command:

    chmod u+x installation-file

    where installation-file is the full pathname to the vCloud Director installation file.
    For example, chmod u+x ./vmware-vcloud-director-1.5.1-622844.bin.
  4. Gracefully shut down the cell as described in KB 1033575.
  5. In a console, shell, or terminal window, run the installation file and type y to upgrade.

    You must type the full pathname to the installation file. For example, ./vmware-vcloud-director-1.5.1-622844.bin.
    As part of the upgrade, the installer unpacks the vCloud Director RPM package, stops vCloud Director services on the server (if they are running), and backs up important configuration files.

  6. Run the /opt/vmware/vcloud-director/bin/upgrade script and type Y when prompted to upgrade the database.
  7. Start the cloud cell by typing the following command:

    service vmware-vcd start

Upgrading a vCloud Director Installation with Multiple Cloud Cells

This scenario describes how to upgrade a vCloud Director installation with multiple cloud cells that are behind a load balancer.

To upgrade a multi-cell installation:

  1. Split the cells into two pools (A and B).
  2. Edit the load balancer configuration so that all traffic is sent to pool A.
  3. Gracefully shut down all cells in pool B (see KB 1033575).
  4. For each cell in pool B, upgrade the cell.
    1. Log in to the target server as root.
    2. Download the installation file to the target server.
    3. Ensure that the installation file is executable.
      The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following command:

      chmod u+x installation-file

      where installation-file is the full pathname to the vCloud Director installation file.
      For example, chmod u+x ./vmware-vcloud-director-1.5.1-622844.bin.
    4. In a console, shell, or terminal window, run the installation file and type y to upgrade.

      You must type the full pathname to the installation file. For example, ./vmware-vcloud-director-1.5.1-622844.bin.
      As part of the upgrade, the installer unpacks the vCloud Director RPM package, stops vCloud Director services on the server (if they are running), and backs up important configuration files.

    5. Run the /opt/vmware/vcloud-director/bin/upgrade script and type Y when prompted to upgrade the database. NOTE: In a multi-cell installation, you only have to perform this step one time.
  5. On one cell (machine C) in pool B, start the maintenance message by typing the following command:
    $VCLOUD_HOME/bin/vmware-vcd-cell maintenance
  6. Edit the load balancer configuration so that all traffic is sent to machine C.
  7. Gracefully shut down all cells in pool A (see KB 1033575).
  8. Start all the cells in pool B by typing the following command for each cell:

    service vmware-vcd start
  9. Edit the load balancer configuration so that all traffic is sent to pool B (except machine C).
  10. On machine C, shut down the maintenance message and then restart the cell:

    service vmware-vcd restart
  11. Edit the load balancer configuration so that all traffic is sent to pool B (including machine C).
  12. For each cell in pool A, upgrade the cell.
    1. Log in to the target server as root.
    2. Download the installation file to the target server.
    3. Ensure that the installation file is executable.
      The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following command:

      chmod u+x installation-file

      where installation-file is the full pathname to the vCloud Director installation file.
      For example, chmod u+x ./vmware-vcloud-director-1.5.1-622844.bin.
    4. In a console, shell, or terminal window, run the installation file and type y to upgrade.

      You must type the full pathname to the installation file. For example, ./vmware-vcloud-director-1.5.1-622844.bin.
      As part of the upgrade, the installer unpacks the vCloud Director RPM package, stops vCloud Director services on the server (if they are running), and backs up important configuration files.

  13. Start all the cells in pool A by typing the following command for each cell:

    service vmware-vcd start
  14. Edit the load balancer configuration so that traffic is sent to all the cloud cells.

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.

The known issues are grouped as follows:

General Issues

"Too many open files" errors
vCloud Director can require high open file limits. Make sure that every cell in your vCloud Director environment allows processes to open more than 1024 files. To see what the current limit is for a cell, log in to the cell, and type ulimit -n. If it says 1024 or less, then take the following steps to increase the open files limit:

  1. Type su -.
  2. Edit /etc/security/limits.conf and make sure it includes the following lines:

    * soft nofile 65535
    * hard nofile 65535
  3. Edit /etc/pam.d/login to include the following line:

    session required pam_limits.so
  4. Type the following command to restart the cell:
    service vmware-vcd restart
  5. Log out of the cell and log back in.
  6. Type ulimit -n to verify your changes.

Cannot change vCloud Director database user name or password while services are running
If you change the vCloud Director database user name or password while services are running, vCloud Director will fail at the next database access and log a message of the form "java.sql.SQLException: ORA-01017: invalid username/password; logon denied". Use the following procedure if you need to change the vCloud Director database user or password:

  1. Stop all vCloud Director services on all cells, as described in the VMware vCloud Director Installation and Configuration Guide.
  2. Using database tools, change the vCloud Director database user or password.
  3. Run the vCloud Director configuration script on all cells, as described in the VMware vCloud Director Installation and Configuration Guide (see "Configuring Network and Database Connections").
    The script first asks for the Java keystore path and password and then prompts you for the new user name/password for the database.

After you complete the script, it updates the information in the vCloud Director database and properties files and re-starts vCloud Director services.

Unable to create a Microsoft Sysprep deployment package
If you get a permission denied error when running the createSysprepPackage.sh script on a cell, you should check to see if SELinux is enabled and running in enforcing mode. To check, run the following command: /usr/sbin/getenforce. If it returns "Enforcing", perform the following workaround to grant the appropriate permissions to run the tool.

Workaround: Enable text-relocation for the shared library used by the script. Run the following command as root after vCloud Director is installed: chcon -t textrel_shlib_t '/opt/vmware/vcloud-director/deploymentPackageCreator/libCreatePkg.so'

Accessing vCloud Director with a Web browser
vCloud Director does not support logging in to different user accounts from the same browser at the same time. If you attempt to do so, the first user is logged out.

Timeout when a provider vDC is created on the same cluster as a VMware Storage Appliance
Creating a provider vDC on the same cluster as a VMware Storage Appliance (VSA) results in a timeout. To avoid this timeout, use the VSA Manager tab of the vSphere Client to put the datastore into maintenance mode. This action stops the VSA virtual machine gracefully and puts its host into maintenance mode. After the host is in maintenance mode, you can use the vCloud Director Web Console to prepare the host.

Cannot create a provider vDC if one or more hosts in a cluster is disconnected
When you create a provider vDC backed by a cluster, all of the hosts in the cluster must be connected. If any host in the cluster is disconnected, the create operation fails.

Workaround: Remove all disconnected hosts from the cluster.

vCloud Director might become unresponsive in Firefox 3.6.x on Windows XP and Windows 2003 systems
When accessing vCloud Director in Firefox 3.6.x on a Windows XP or Windows 2003 system, the UI becomes unresponsive after clicking Browse for a vApp template or media upload. To fix this issue, click in your browser's search or URL bar, then back in the vCloud Director web UI.

Cannot create a vApp if vCenter has more than 2000 port groups
If a vCenter Server has more than 2000 standard or distributed port groups, you cannot create a vApp on any organization vDC that uses that vCenter Server. This limitation applies only to vCloud Director installations using SQL Server.

Console proxy causes high CPU and memory load on vCD cells
Increased resource consumption by the console proxy can cause high CPU and memory load on vCD cells. If you see high CPU and memory load on vCD cells, increase the number of cells and file descriptors. To increase the number of file descriptors, see Accessing the vCloud Director user interface fails with the error: Cannot open connection - Too many open files.

vCenter Chargeback 1.6.2 and 2.0.x supported only by vCloud Director 1.5.x
vCenter Chargeback 1.6.2 and 2.0.x are supported only by vCloud Director 1.5.x and will not work with earlier versions of vCloud Director.

Workaround: Upgrade vCloud Director to version 1.5.x before installing vCenter Chargeback 1.6.2 or 2.0.x.

Installation and Upgrade Issues

Server reboot required after upgrading vCloud Director
After you upgrade vCloud Director software on any member of a server group, you must run the script in /etc/profile.d/vcloud.sh, so that the vCloud Director environment is initialized with the proper values. Alternatively, you can log out of the server and then log in again.

vCloud Director reports host spanning is out of date after upgrading ESX
After you upgrade an ESX host managed by vCloud Director, the vCloud Director Web Console reports that host spanning is out of date for this host and prompts the system administrator to repair the host. In most cases, this condition clears itself within a few minutes without a repair action. Refresh the page to check the status of the upgraded host.

Unable to open vCD after upgrade
Upgrading resulted in an SWF update. In some cases, the server-side flash SWF does not update properly due to caching.Workaround: Clear your flash cache.

  1. Go to the Adobe Settings Manager.
  2. Click Delete all sites.
  3. Click Confirm.

Upgrading vCloud Director interrupts in-progress OVF and media image uploads
In-progress uploads of OVF packages and media images can fail if interrupted by a vCloud Director upgrade. Failed uploads can be re-started after the upgrade completes.

vCloud Director servers and database must be in the same time zone
See Configure vCloud Director servers and database to be in the same timezone.

I18N Issues

ja_JP locales and Oracle
If you want to use a ja_JP locale for your vCloud Director cells and you want to use an Oracle database, make sure that you do not set "JA16SJISTILDE" as the NLS_CHARACTERSET.

Guest customization tab does not support non-ASCII characters
You cannot enter non-ASCII characters into any of the text fields on the Guest Customization tab of the Virtual Machine Properties page. This includes the local administrator password; the domain name and its user name and password; and the customization script.

Cannot create organization with non-ASCII characters
vCloud Director does not support non-ASCII characters in organization names.

Uploading a vApp template with a long name containing unicode characters fails
When you try to upload a vApp template with a long name that includes unicode characters, the upload operation fails. If you encounter this issue, shorten the vApp template name and retry the upload operation.

Non-ASCII characters in a system name might cause NAT-routed external organization network creation to fail
When you create an external organization network with a NAT-routed connection, the system name should contain only ASCII characters. Non-ASCII characters in the system name might cause network creation to fail.

Networking Issues

Default lease time UI field is non-functional
Entering a value into the DHCP Default lease time UI field does not have any effect on a vApp's DHCP configuration.

Editing a virtual machine in certain vApp networks causes NAT mappings to be added for every virtual machine NIC on the network
When you edit any virtual machine on a fenced or routed vApp network that uses IP Translation, NAT mappings are added for every virtual machine NIC on the network.

Outgoing traffic filtering fails with vShield Edge 4.1 in fenced mode
Traffic filtering in vShield Edge 4.1 in fenced mode fails with this release of vCloud Director, allowing all outgoing traffic even when the outgoing traffic rule is set to DENY.

Norton Internet Security blocks installation of the VMware VMRC plugin
The VMRC plugin is required in order to view vCloud Director virtual machine consoles. Follow the Norton Internet Security procedures to allow the VMRC plugin to be installed.

Cannot install VMware VMRC plugin for Mozilla Firefox
On certain Linux operating systems, you may not be able to install the VMRC plugin for Firefox. You can take the following steps to resolve the issue:

  1. After downloading the VMRC plugin, run the installer and change the default installation path to /usr/lib/mozilla/plugins.
  2. Complete the installation wizard.
  3. Run the following commands to change the link to the plugin:
    • Go to the Mozilla plugins directory: cd /usr/lib/mozilla/plugins
    • Remove the invalid symbolic link: rm -f np-vmware-vmrc-e.x.p-378321.so
    • Create a valid link: ln -s /user/lib/vmware-vmrc/np-vmware-vmrc-e.x.p-378321.32.so no-vmware-vmware-vmrc-e.x.p-378321.so
    • Verify the link: ls -la

VMRC crashes while opening the console when Visual C++ 8 runtime is not present
When you open the console in an environment without Visual C++ 8 runtime, the VMRC plugin crashes. To restore console functionality, install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)'vcredist_x86'.

Organization vDC Issues

Cannot start a vApp in a Reservation Pool organization vDC
Users can set memory and CPU reservations for their virtual machines in a Reservation Pool organization vDC. As a result, it is possible for users to reserve all the available memory and CPU in the organization vDC for their virtual machines. In this case, they would not be able to start a vApp that requires a vShield Edge virtual machine to provide network services, since there would be no memory or CPU available.

Upload and Download Issues

Java plug-in issues
In order to upload vApp templates and media to a catalog, the computer from which you are uploading must have Java Plug-in 1.6.0_10 or later installed. In some cases, even after you install the plug-in you will not be able to upload files until you restart your Web browser.

Virtual Machine Issues

Trouble viewing virtual machine consoles with Internet Explorer on Windows Vista and later
You may experience problems when trying to view a virtual machine console with Internet Explorer from a computer running Windows Vista or later. Disabling Internet Explorer's Protected Mode resolves this issue.

Cannot click Client Integration Access Control Dialog
When you use the Open Console command to view a virtual machine console, the Client Integration Access Control dialog displays. For certain operating system and browser combinations, you may not be able to click in the dialog until you first click in the virtual machine console.

No warning is given when the VMRC organization connections limit is reached
When the VMRC organization connections limit is exceeded, a blank console is displayed. No error message is given. If you encounter this error, contact your organization administrator.

An attached device might not appear as attached after a console refresh
In some cases, when you refresh a console while a device is connected, the device remains attached after the refresh, but does not display as attached. The device remains connected even if you open a manage device dialog box and leave None selected.

To re-synchronize the UI with the device connection state, connect the device again in the UI. A message appears that the device is already connected. After this message appears, device management operations behave correctly again.

Console does not load correctly in Firefox 3.6 on Windows systems
In Firefox 3.6 running on Windows systems, the console does not display in windowed mode. To get the console to display correctly, use the console in full screen mode.

Console does not reconnect when a virtual machine is powered on from outside the console window
When you leave a console window open after shutting down a virtual machine and the virtual machine is powered on again from outside the console, the console does not reconnect to the powered on virtual machine. To reconnect the console to the virtual machine, close the console and open a new console window for the virtual machine.

Console might not display correctly in Internet Explorer 9 on Windows 7 systems
When you open a console in Internet Explorer 9 on a Windows 7 system, it might display a gray screen instead of the virtual machine desktop. To correct this display issue, refresh the console page.

NIC deletion does not resolve until you click OK
When you delete a NIC, click OK before editing any other properties. Editing other properties before you click OK might result in misconfigured NICs.

Notification and Extension Issues

Spurious notification for catalog delete events
If notifications are enabled and a catalog is deleted, two notifications are sent: one for a /catalog/modify event and one for a /catalog/delete event. The catalog/modify event is a spurious notification and can be ignored.

vCloud API Issues

  • The schema definitions included in approvals.xsd are no longer supported.

  • A vApp that displays as "Fenced" in the UI may have its vApp network Configuration FenceMode displayed as "natRouted" when retrieved in the vCloud API. If the IP subnet on the vApp network overlaps the IP subnet on the external network, then the vApp is actually deployed fenced. If the IP subnets on the two do not overlap, it is natRouted.

  • When a cloneVappTemplate request is made with the vCloud API, the value of the name attribute in the request body is ignored, and the cloned object retains the name of the Source object.

  • When a cloneVapp request is made with the vCloud API, the deploy and powerOn attributes in the request body are ignored.

  • Attempts to use the vCloud API to specify a memory reservation or limit when editing the VirtualHardwareSection of a Vm are silently ignored when the Vm is in a vDC whose AllocationModel has the value AllocationPool or AllocationVapp.

  • If you encounter errors (for example, "OperationDeniedException - Operations not in users context") when using the vCloud API to import LDAP users into an organization, log out and log in, then try to import the users again.

  • When you instantiate a vApp template and specify a FenceMode value of isolated, the vApp network is created with a FenceMode of natRouted.

  • When you configure the networkUpdateNetwork operation as a blocking task, no blocking task will be created when a vApp network is updated.

  • If you abort or fail a blocking task for 'vdcRecomposeVapp' operation, changes to some sections, including the LeaseSettingsSection, might not be reverted. You must revert the changes manually by reconfiguring the vApp.

  • Be sure to deploy vShield Edge virtual machines in vCenter clusters that have adequate resources. If you do not, the vShield Edge virtual machine can fail to start. When this happens, vCloud Director displays a message of the form:

    Unable to start vApp "----".
    - Unable to start virtual machines in resource pool "----".
    - Failed to initialize shield appliance
    - HTTP/1.1 400 Bad Request
    Code : 70510, Description : Unable to power on vShield Edge VM

  • You cannot filter the result set of a datastores query by matching the value of the provisionedStorageMB record, as shown in this example, which selects no records, regardless of the actual values of the provisionedStorageMB records in the result set.

    GET https://vcloud.example.com/api/query?type=datastore&fields=provisionedStorageMB&filter=provisionedStorageMB==460

Resolved Issues

Cannot compose a vApp or add a virtual machine to a vApp after upgrading from vCloud Director 1.x to 1.5
After upgrading from vCloud Director 1.x to 1.5, you may see the error Invalid computer name: Computer name can only contain alphanumeric characters, hyphens and underscores, and must not contain only digits.. This issue is resolved for vCloud Director 1.5.1.

vCloud Director Web interface displays erroneous entries when an LDAP-based Organization Administrator creates a catalog or catalog item
When an Organization Administrator (Org Admin) logs in to a vCloud Director (vCD) organization and creates a catalog or catalog item, such as vApp template, the new entry is repeated multiple times in the vCD Web interface under the following conditions:

  • The Org Admin user is based on an LDAP account.
  • The Org Admin is also an administrator in other organizations.
This issue is resolved for vCloud Director 1.5.1.

Cannot edit/delete vApps, media, or templates after upgrading from vCloud Director 1.0.x to 1.5
If the log files contain an error similar to java.lang.IllegalArgumentException: Unknown name value for enum class com.vmware.vcloud.common.model.TaskOperation: VDC_UPDATE_RESOURCE_ENTITY, refer to Knowledge Base (KB) article 2006704. This issue is resolved for vCloud Director 1.5.1.

Some host names are rejected as invalid as the Public Console Proxy Address
In vCloud Director 1.5, certain host names that included one or more digits were considered invalid when entered as the Public Console Proxy Address. For example, vcloud.123example.com or 123.vcloudexample.com. This issue is resolved for vCloud Director 1.5.1.

vCloud Director displays a host alert when a vSphere standard switch without uplinks is present
When a host has a vSphere standard switch that has no uplink (physical NIC), vCloud Director 1.5 displayed the alert "The host is not connected to the following vSwitches: [standard switch name]." This issue is resolved for vCloud Director 1.5.1.

Networking issues on virtual machines running certain guest operating systems
This release fixes an issue that affected some vCloud Director virtual machines running on ESX/ESXi 4.1 hosts. For virtual machines created with the following guest operating systems, vCloud Director set the incorrect network adapter type (Flexible instead of E1000):

  • Microsoft Windows 7 (32 bit)
  • Microsoft Windows Vista (32 bit)
  • Microsoft Windows Server 2003 Enterprise Edition (32 bit)
  • Microsoft Windows Server 2003 Datacenter Edition (32 bit)
  • Microsoft Windows Server 2003 Standard Edition (32 bit)
  • Microsoft Windows Server 2008 (32 bit)
  • Suse Linux Enterprise 11 (32 bit)
  • Debian GNU/Linux 5 (32 bit)
  • Debian GNU/Linux 4 (32 bit)
  • Novell Netware 6.x
  • Novell Netware 5.1
  • Sun Solaris 10 (32 bit)
  • Sun Solaris 9 (experimental)
  • FreeBSD (32 bit)

vCloud Director 1.5.1 resolves this issue.

RetainNetInfoAcrossDeployments element cannot be updated using the REST API
In vCloud Director 1.5, you could not update the RetainNetInfoAcrossDeployments element using the REST API. This issue is resolved for vCloud Director 1.5.1. In addition, setting the value of the element to "true" now preserves the external IP addresses associated with a network's NAT rules.

Interactions between RetainNetInfoAcrossDeployments REST API element and "Always use assigned IP addresses..." check box in the UI
The RetainNetInfoAcrossDeployments element in the REST API can be set for specific networks. The "Always use assigned IP addresses until this vApp or associated networks are deleted" setting in the UI applies to all networks in a vApp. In vCloud Director 1.5.1, selecting "Always use assigned IP addresses..." in the UI will set the RetainNetInfoAcrossDeployments element to "true" for all the networks in the vApp. Setting the RetainNetInfoAcrossDeployments element to "true" for a specific network will only select the "Always use assigned IP addresses..." check box in the UI if all other networks in the vApp also have the RetainNetInfoAcrossDeployments element set to "true".

Creation of shadow virtual machines failing
This release fixes an issue that could cause the creation of shadow virtual machines to fail.

vApp template download fails with a "NullPointerException" error
In vCloud Director 1.5, downloading a vApp template that includes a virtual machine with media attached results in a failed download. vCloud Director 1.5.1 resolves this issue. NOTE: The vApp template download succeeds, but the media information is not retained after the download.

System administrators cannot connect to the ActiveMQ broker network
This release fixes an issue that prevented system administrators from connecting to the ActiveMQ broker network using a JMS client.

Provider vDC creation/host preparation fails with "Could not retrieve state for sequence:seq_os" error
These failures occurred in environments using a Microsoft SQL Server database with case sensitive collation in combination with ESX/i 4.1 Update 1 and later and ESX/i 4.0 Update 3 and later. vCloud Director 1.5.1 resolves this issue.

Download Windows Remote Desktop Shortcut File menu item is unavailable
In vCloud Director 1.5.1, you can now select this menu item for powered on virtual machines running a Windows guest operating system.

Cannot reset an organization network after upgrading from vShield Manager 4.1 to 5.0
In vCloud Director 1.5, under certain circumstances, you could not reset a routed organization network after upgrading from vShield Manager 4.1 to 5.0. In vCloud Director 1.5.1, under the same circumstances, vCD will report the error "vShield Manager has been upgraded recently, retry operation.". When you retry the operation, vCD resets the network with no error.

Cannot upgrade virtual hardware version for a vApp
In vCloud Director 1.5, upgrading the virtual hardware version for a vApp with a vApp network connected to an organization network could fail with the error "could not serialize". vCloud Director 1.5.1 resolves this issue.

SCSI ID 7 is available for virtual machine hard disks
In vCloud Director 1.5, you could select SCSI ID 7 in the Unit Number drop-down list for hard disks on the virtual machine properties page, even though SCSI ID 7 is reserved. The vCloud Director 1.5.1 UI reflects the fact that SCSI ID 7 is not available for use.