Released: vCloud Director SP 8.0.1
There is also increased supportability for vSphere, NSX and vCNS. vCD 8.01 now supports vSphere versions 6.0U2, 6.0U1, and 5.5U3, NSX versions 6.2.2, 6.2.1, 6.1.6, and 6.1.5 and vCloud Networking and Security versions 18.104.22.168 and 22.214.171.124.
As usual I’ve gone through the Resolved Issues list and highlighted the ones I feel are most relevant…the ones in red are issues we have seen in our vCloud Zones and Zettagrid Labs.
- vCloud Director Web client incorrectly displays a pending status for some objects
When you select an object such as a virtual data center, network, or Edge gateway in the left pane of the vCloud Director Web client, vCloud Director sometimes incorrectly displays a status of Pending. This occurs when no actions have been performed on the object within the time limit set to clean up audit event data.
- Attempts to add a second external network to an Edge gateway fail
When you attempt to add a second external network to an Edge gateway, the operation fails with the following error message.
Violation of UNIQUE KEY constraint 'uq_plac_subj_ite_su_id_i_u_i_t'. Cannot insert duplicate key in object 'dbo.placement_subject_item'.
- vCloud Director does not migrate virtual machine after switching to a storage policy with SDRS disabled
After you modify a virtual machine to use a storage policy with a datastore that has SDRS disabled, vCloud Director fails to migrate the virtual machine.
- Attempts to change the storage policy of a virtual machine on a storage cluster sometimes fail
When you attempt to change the storage policy of a virtual machine on storage cluster sometimes fail with an error message similar to the following.
Could not execute JDBC batch update; SQL [insert into placement_subject_item (existing_item, item_type, item_uri, subject_id, target_uri, id) values (?, ?, ?, ?, ?, ?)]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
- Could not execute JDBC batch update
- vCloud API incorrectly returns a virtual machine snapshot size of
When you use the vCloud API call
SnapshotSection, the vCloud API incorrectly returns a snapshot size of
There are still a bunch of Unresolved Issues with workarounds but again shows the commitment to continuing to mature the platform…looking forward to the enhancements coming in the next major release. For those with the correct entitlements…download here.