VMware

vCloud Director 5.5.3 Release Notes

vCloud Director 5.5.3 | 23 MAR 2015 | Build 2578696

Last updated: 21 APR 2015

What's in the Release Notes

The release notes cover the following topics:

What's New

  • Disable virtual machine licensing collection: Update the config table of your database to disable virtual machine licensing collection.

    Disable virtual machine licensing collection on a Microsoft SQL Server database
    Add the following to the database config table.

    INSERT INTO config (cat, name, value) VALUES ('vcloud', 'licensing.metrics.vm.enabled', 'false');

    Disable virtual machine licensing collection on an Oracle database
    Add the following to the database config table.

    INSERT INTO config (config_id, cat, name, value) VALUES (seq_config.nextval, 'vcloud', 'licensing.metrics.vm.enabled', 'false');
    COMMIT;

  • Increased guest operating system support: vCloud Director has added support for the following guest operating systems.
    • Red Hat Enterprise Linux 6.6
    • Ubuntu 14.10
  • Increased guest operating system customization support: vCloud Director has added customization support for the following guest operating systems.
    • Red Hat Enterprise Linux 6.6
    • Ubuntu 14.10
    • CentOS 7.0 (64-bit)
    • Oracle Linux 7.0 (64-bit)

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.3 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

  • JRE Updated
    The Oracle (Sun) JRE package is updated to 1.7.0_76. The update addresses multiple security issues that exist in the earlier releases of Oracle (Sun) JRE. Oracle has documented the CVE identifiers that are addressed in JRE 1.7.0_76 in the Oracle Java SE Critical Patch Update Advisory for January 2015.

  • vCloud Director displays some catalogs' status as Unknown after you upgrade vCloud Director from version 5.1.x
    After you upgrade vCloud Director from version 5.1.x, vCloud Director displays the status of some catalogs that were present before the upgrade as Unknown and displays those catalog names highlighted in gray. This issue occurs when the catalog has existed for longer than the activity log of vCloud Director, and the task might have been deleted from the database resulting in a catalog status of unknown. This issue is resolved in vCloud Director 5.5.3.

  • Deleted users are not marked as stranded after LDAP synchronization
    When vCloud Director automatically synchronizes user and group information with the LDAP server, deleted users are not marked as stranded. This issue is resolved in vCloud Director 5.5.3.

  • Creating or querying a member of an imported group returns groups of the same name in other organizations
    After you import a group into multiple organizations, when you create or query a user that is a member of the imported group in one organization, vCloud Director returns groups of the same name from other organizations. This issue is resolved in vCloud Director 5.5.3.

  • Company name field does not validate input for scripts
    After a system administrator types JavaScript into the company name field in the vCloud Director Web client, the script is executed when you log into or out of vCloud Director through the vCloud Director Web client. vCloud Director 5.5.3 does not execute scripts typed into the company name field.

  • Attempts to delete an independent disk from the Media page of the vCloud Director Web client leave the database in an inconsistent state
    When you attempt to delete an independent disk from the Media page of the vCloud Director Web client, vCloud Director displays a null pointer error message, and the database is left in an inconsistent state. In vCloud Director 5.5.3, independent disks are not displayed on the Media page of the vCloud Director Web Client.

  • Attempts to download vApp templates from a shared catalog fail
    When you attempt to download a vApp template from a catalog that is shared from another organization, the operation fails. This issue is resolved in vCloud Director 5.5.3.

  • Attempts to download media files from a public catalog fail
    When you attempt to download a media file from a public catalog, the download operation fails. This issue is resolved in vCloud Director 5.5.3.

Networking Issues

  • Logging is disabled for IPsec VPNs and edge gateway High Availability
    Logging is disabled for IPsec VPNs and edge gateway High Availability. vCloud Director 5.5.3 enables logging for these edge gateway features. This logging setting applies to all edge gateways in the cloud environment.

  • Adding or removing an external network from an edge gateway in vCloud Director disrupts networking service
    When you add or remove an external network from an edge gateway in vCloud Director, the networking services provided by the edge gateway are disrupted. This issue is resolved in vCloud Director 5.5.3.

  • Virtual machine NIC is disconnected when you revert to a snapshot
    When you revert a virtual machine to a snapshot, the virtual machine's NIC is disconnected. This issue is resolved in vCloud Director 5.5.3.

Virtual Machine and vApp Issues

  • vApp network name changes do not appear in edge gateways
    When you change the name of a vApp network in vCloud Director, the original name continues to appear in the edge gateway. This issue is resolved in vCloud Director 5.5.3.

  • Attempts to power on a vApp sometimes fail with a distributed port group error
    When you attempt to power on a vApp, the operation sometimes fails with an error similar to the following.

    DV portgroup is not found in the inventory after creation.

    This issue is resolved in vCloud Director 5.5.3.

  • Extra IP addresses assigned to a vApp template when you copy or move the template between catalogs
    When you copy or move a vApp template from one catalog to another, vCloud Director assigns additional IP addresses to the vApp template from the available IP pool. This issue is resolved in vCloud Director 5.5.3.

  • Deploying a vApp fails after you merge provider virtual data centers when you use VCloud Director 5.5.x with vSphere 6.0
    After you merge two provider virtual data centers when you are using vCloud Director 5.5.x with vSphere 6.0, attempts to deploy a vApp in an organization that belongs to the merged provider virtual data center fail with a null pointer error message. This issue is resolved in vCloud Director 5.5.3.

  • The Upload new version menu option does not work in Firefox or Internet Explorer browsers
    When using a catalog's Catalog page in the vCloud Director Web client in a Firefox or Internet Explorer browser, clicking the Upload new version menu item on a selected vApp template or media file fails to open the dialog for uploading a new versio. This issue is resolved in vCloud Director 5.5.3.

  • Attempts to power on vApps fail when virtual machine properties are undefined in vCenter Server
    When certain virtual machine properties are undefined in vCenter Server, attempts to power on the vApp fail. This might occur after you upgrade vCloud Director from version 5.1.x to version 5.5.x. This issue is resolved in vCloud Director 5.5.3.

  • Guest customization fails with a Sysprep error
    When you attempt to use guest customization on a virtual machine, the operation fails with the following error message.

    Mount directory C: does not exist

    This issue is resolved in vCloud Director 5.5.3.

  • Attempts to open a virtual machine console on Google Chrome fail
    When you attempt to open a virtual machine console on a Google Chrome browser, the operation fails. The occurs due to the deprication of NPAPI in Google Chrome. vCloud Director 5.5.3 uses WebMKS instead of the VMware Remote Console to open virtual machine consoles in Google Chrome, which resolves this issue.

vCloud API Issues

  • Name attribute missing when you use the vCloud API to remove a virtual machine from a vApp
    When you use the vCloud API to remove a virtual machine from a vApp, the name attribute is missing from the task XML. This issue is resolved in vCloud Director 5.5.3.

Known Issues

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

  • vApp creation failures when storage DRS is enabled
    When you use vCloud Director 5.5.3 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.

    Workaround: Disable storage DRS on vSphere 6.0.

  • 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 5.5.3 with vSphere 6.0.

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

  • 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.

  • 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.

  • 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.3, 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.

  • 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.