VMware

vCloud Director 5.5.4 Release Notes

vCloud Director 5.5.4 | 9 JUL 2015 | Build 2831206

Last updated: 22 FEB 2016

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Removed configuration restrictions for virtual machine NICs: This release removes most restrictions on removing or reconfiguring a VM's primary NIC for hardware version 7 and later. You still cannot remove the primary NIC if it is connected to a VCDNI-backed network. If you reconfigure a VM's primary NIC to connect it to a different network, the VM will lose network connectivity if the new network has a different IP configuration (subnet, netmask, gateway, and so on). To restore network connectivity, you open a Virtual Machine Console and change the network settings. See KB 2123453.
  • Updated Java Runtime Environment version: vCloud Director 5.5.4 uses Java Runtime Environment version 1.7 update 80.

System Requirements and Installation

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

You can use vCloud Director 5.5.4 with vSphere 6.0, but features that are new to vSphere 6.0 do not work with VCD 5.5.3. See What's New in the vSphere 6.0 Platform. To use vCloud Director 5.5.3 with vSphere 6.0, you must also use vCloud Networking and Security 5.5.4 or NSX 6.1.3.

Documentation

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

Resolved Issues

This release resolves the following issues.

General Issues

  • vCloud Director fails to send notification email alerts for database connection failure and restoration
    When vCloud Director loses or restores a connection to the database, vCloud Director fails to send a notification email to the system administrator. This issue is resolved in vCloud Director 5.5.4.

Networking Issues

  • Virtual machine NIC incorrectly set to None in vCenter Server during vApp deployment in vCloud Director
    When you deploy a vApp, the virtual machine NIC is sometimes incorrectly set to None in vCenter Server while it shows as assigned to a VXLAN network in vCloud Director. This issue is resolved in vCloud Director 5.5.4.

  • Virtual machine network connectivity is disrupted when you disable firewall on an edge gateway by using vCloud Director
    When you use vCloud Director to disable firewall on an edge gateway, network connectivity for virtual machines associated with the edge gateway is disrupted. This issue is resolved in vCloud Director 5.5.4.

Virtual Machine and vApp Issues

  • Some commands fail in a SUSE Linux virtual machine after applying guest customization
    After you apply guest customization on a virtual machine running a SUSE Linux operating system, the following commands fail if the computer name contains a . character.

    hostname -f
    hostname -i
    hostname -d

    This issue is resolved in vCloud Director 5.5.4.

  • vCloud Director displays two listings for the same organization virtual data center network during vApp creation
    When you create a vApp from a catalog template, vCloud Director displays the same organization virtual data center network name twice in the list of available organization virtual data center networks to use for the vApp. This issue is resolved in vCloud Director 5.5.4.

  • vApp creation failures when storage DRS is enabled
    When you use vCloud Director with vSphere 6.0, any operation that clone a vApp, including add to my cloud, instantiate a vApp template, copy, relocate, or import a vApp might fail when the target virtual data center includes a storage DRS-enabled storage cluster that does not support source virtual machine's storage profile. This failure logs a message similar to the following.

    Could not find datastore to create VM ...
    Cannot use datastore [vcId=nnnn, moref=datastore-nn] since it does not support storage policy SDRS_SP.

    This issue is resolved when you use vCloud Director with vSphere 6.0b.

  • vCloud Director incorrectly names virtual machine files after you deploy a vApp across instances of vCenter Server
    When you deploy a vApp across instances of vCenter Server, vCloud Director incorrectly renames the virtual machine, virtual machine files, and virtual machine folder, then assigns the correct name to the virtual machine in the vCloud Director web client. This results in the virtual machine files and folder having a different name on the datastore than they do in the vCloud Director web client. This issue is resolved in vCloud Director 5.5.4.

  • Virtual machine's fully qualified domain name is set incorrectly after guest customization
    After you apply guest customization to a Linux virtual machine, vCloud Director sets the virtual machine's fully qualified domain name incorrectly. This issue is resolved in vCloud Director 5.5.4.

  • Attempting to deploy a vApp template with 4 IDE disks across instances of vCenter Server fails
    When you attempt to deploy a vApp template with 4 IDE disks to an organization virtual data center backed by a different instance of vCenter Server than the vApp was created on, the operation fails with the following error message.

    No available IDE slot for the new IDE hard disk

    This issue is resolved in vCloud Director 5.5.4.

  • Incorrect memory reservation system alert
    vCloud Director sometimes displays the following system alert for a vApp even when the virtual machine's memory reservation has not been modified.

    System Alert - Virtual Machine's memory reservation was modified.

    This issue is resolved in vCloud Director 5.5.4.

  • Attempts to change a virtual machine's quota fail when the LDAP user's phone number is longer than 31 characters
    When you attempt to change a virtual machine's quota when the LDAP user's phone number is longer than 31 characters, the operation fails with the following error message.

    validation error on field 'phoneNumber': String value has invalid length for TELEPHONE_NUMBER - 31

    This issue is resolved in vCloud Director 5.5.4.

  • CPU cores per socket is set to 1 when you deploy a virtual machine from a template
    When you deploy a virtual machine from a template, vCloud Director sets the number of CPU cores per socket for the virtual machine to 1. This issue is resolved in vCloud Director 5.5.4.

Known Issues

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

General Issues

  • Attempts to upload or download an OVF or configure joint IPSEC VPN on Google Chrome fail
    When you try to use the vCloud Director Web Console in the Google Chrome browser to perform an OVF upload or download operation, or configure joint IPSEC VPN, a message might appear saying that the operation is not supported in your browser.

    Google Chrome no longer supports OVF upload/download due to the removal of the NPAPI support within Chrome.

    Workaround: To perform OVF upload or download operations, use the VMware OVF Tool. The OVF Tool and its User Guide are available on the OVF Tool Documentation page.

    Instead of configuring IPSEC VPN jointly, configure them separately. See Create a VPN Tunnel to a Remote Network.

Localization and Globalization Issues

  • vSphere SSO users whose user names include non-ASCII characters cannot log in to vCloud Director after they are imported
    When a user defined by the vSphere SSO service has a user name that includes non-ASCII characters, the user name is not decoded correctly when the imported user logs into the system, resulting in log in failure. This issue occurs only when you use vCloud Director with vSphere 6.0.

    Workaround: Change usernames to use only ASCII characters before using vSphere SSO to import users.

  • Host agent upgrade fails if the vCloud Director system name contains non-ASCII characters
    When you upgrade a vCloud Director system with non-ASCII characters in its name from an earlier version to version 5.5.4, the host agent upgrade fails.

    Workaround: Unprepare the host to remove the host agent, then prepare the host agent again.

  • Some localized messages appear 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 appear in English.

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

  • A CD or DVD device name containing non-ASCII characters causes attempts to add the CD or DVD to a virtual machine to fail
    Attempts to add a CD/DVD device with non-ASCII characters in its name to a virtual machine fails.

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

  • Non-ASCII characters in VPN tunnel names appear as garbage characters in remote organizations
    When you assign a name to a VPN tunnel that 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.

  • 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 locales other than English, object lists can be filtered only by columns that contain user-generated content
    When you use vCloud Director in locales other than English, the filter function on object lists only works when you filter using columns that contain user-generated content, such as Name or vApp Name.

  • Repeated prompts to install the VMware Client Integration Plug-in appear when importing a file into a catalog or opening a virtual machine console from a Windows account that contains non-ASCII characters
    When you attempt to import a file into a vCloud Director catalog or open a virtual machine console from a Windows account that has non-ASCII characters in its name, vCloud Director prompts you to install the VMware Client Integration Plug-in. This happens even when the plug-in is already installed.

    Workaround: Log in to the Windows administrator account or a user account that contains only ASCII characters in its name, and upload the file or open the virtual machine.

Virtual Machine and vApp Issues

  • Reboot might fail on Ubuntu 14.10 virtual machine after applying guest customization
    After you apply guest customization to a virtual machine running an Ubuntu 14.10 guest operating system, attempting to reboot the virtual machine might fail with the following error message.

    start: Job failed to start

    Workaround: Reset the virtual machine.

    1. Click My Cloud.
    2. In the left pane, select vApps or VMs.
    3. Right-click the vApp or virtual machine, and select Reset.
  • A virtual machine's popped-out console displays a blank screen with disconnected status when using the Google Chrome or Mozilla Firefox browsers and the virtual machine's name uses non-ASCII characters
    When you are using the Google Chrome or Mozilla Firefox browser and you pop out a virtual machine's console from the vCloud Director Web Console, the console might display a black screen and disconnected status if the virtual machine's name contains non-ASCII characters.

    Workaround: Use Microsoft Internet Explorer browser to open the virtual machine's console.

API Issues

  • Load balancer pools cannot be modified on an individual basis using the vCloud API
    Currently you cannot add, remove, or edit a load balancer pool by using the vCloud API. Modifications made to one load balancer pool by using the vCloud API affect all load balancer pools.

  • Attempts to delete a metadata key using the vCloud API fail if the value of the metadata Key element, the key name, contains an ampersand (&)
    When a metadata key name contains an ampersand (&), attempts to delete the metadata using the vCloud API fail unless the deletion link is parsed to replace the reserved character with its percent-encoded representation.

    Workaround: Use the vCloud Director user interface to delete metadata where the key name contains an ampersand.