VMware vCloud Director 1.5.2 released

VMware just released a update for vCloud Director 1.5

Release Notes:

https://www.vmware.com/support/vcd/doc/rel_notes_vcloud_director_152.html

Download:

https://my.vmware.com/web/vmware/details?downloadGroup=VCD152&productId=177&rPId=3227

What’s New:

  • Improvements to virtual machine popout console
    vCloud Director 1.5.2 adds a new button to the virtual machine popout console. The Fit Window to Guest button resizes the console screen to match the screen resolution of the guest operating system.

Resolved issues(Partial):

  • Two vApps within an organization can have the same name after upgrading vCloud Director
    After upgrading from vCloud Director 1.0.x to 1.5 or 1.5.1, you are able to create a vApp with the same name as another vApp in an organization. This issue is resolved for vCloud Director 1.5.2, which ensures that each vApp within an organization has a unique name.
  • Multiple virtual machines in vCloud Director can reference a single virtual machine in vSphere
    In vCloud Director 1.5.1, it was possible to import the same virtual machine from vSphere into more than one vApp in vCloud Director. The situation could occur when the virtual machine was removed from the vCenter Server inventory and then added back to the inventory. This issue is resolved in vCloud Director 1.5.2.
  • The UI freezes when using a non-English client browser to connect to vCloud Director
    In certain circumstances, the vCloud Director 1.5.1 UI could become unusable when viewing log events from a non-English client browser. This issue is resolved in vCloud Director 1.5.2.
  • Blocking tasks initiated by a System Administrator do not appear in the list of blocked tasks
    In vCloud Director 1.5.1, blocking tasks performed by System Administrator are not shown in the list of blocked tasks and as a result, there is no way to abort or resume the task from UI. vCloud Director 1.5.2 fixes this issue.
  • Cannot open the virtual machine console for certain VMs
    In vCloud Director 1.5.1, you could not open the virtual machine console for a VM based on a vApp template that was uploaded from an OVF file larger than 128KB. vCloud Director 1.5.2 fixes this issue.
  • Guest customization issues
    In vCloud Director 1.5.1, when performing guest customization on a virtual machine, network configuration was performed after sysprep. As a result, virtual machines were not able to access a network during customization. vCloud Director 1.5.2 fixes this issue.
  • Cannot view or modify vSphere port group-backed network pools
    After upgrading from vCloud Director 1.0 or 1.0.1, you were unable to view or edit port group-backed network pools in vCloud Director 1.5 and 1.5.1. vCloud Director would display an “Unknown Error” while editing the properties of these network pools. This issue is resolved in vCloud Director 1.5.2.
  • Users list shows no users and an error displays
    Sorting the Users list on the Locked column in vCloud Director 1.5 and 1.5.1 results in an empty list and the following error: “could not resolve property: locked of: com.vmware.vcloud.api.presentation.entity.query.UserQueryListData”. This issue is resolved in vCloud Director 1.5.2.
  • Cannot upload an OVF as a vApp template
    In vCloud Director 1.5.1, when you upload an OVF file as a vApp template, the upload could fail. In some circumstances, vCloud Director would choose a network that is not accessible to the resource pool to which the OVF is uploaded, resulting in the failure. This issue is resolved in vCloud Director 1.5.2.
  • IP addresses not being released for reallocation
    Released IP addresses were not cleaned up in vCloud Director 1.5.1, even after the IP address release timeout. The IPs were cleaned up only during the vApp creation workflow and not during the workflow of adding IPs to the list of external IPs for an organization network. vCloud Director 1.5.2 fixes this issue.
  • Incomplete list of vApp templates displayed in catalog
    In vCloud Director 1.5.1, vApp templates with their storage lease set to Never Expires did not display in the catalog. vCloud Director 1.5.2 fixes this issue.
  • Adding a virtual machine to a vApp fails with “Unknown Error”
    In vCloud Director 1.5 and 1.5.1, adding a new virtual machine to a vApp could fail after a virtual machine in the vApp was deleted or moved to another vApp. vCloud Director 1.5.2 fixes this issue.
Advertisements
By Rotem Agmon Posted in Info

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s