VMware vCloud Availability for vCloud Director 1.0.1.4 | 18 JAN 2018 | Build 7603162

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This patch release delivers bug fixes to enable service providers to move replications between standalone datastores and clustered datastore by using either the scripts available on the vCloud Availability Installer appliance or the vCloud Availability Administration Portal.

Browser Support

The vCloud Availability Administration Portal 1.0.1.4 supports the following Web browsers:

  • Google Chrome 62.0.3202.94 (Official Build) (64-bit)
  • Mozilla Firefox 57.0.1 (64-bit)
  • Mozilla Firefox 57.0.1 (32-bit)

Upgrade

To upgrade your vCloud Availability environment to version 1.0.1.4, you must upgrade the vCloud Availability Installer and the vCloud Availability Administration Portal appliances. All other components remain unchanged.

Upgrading the vCloud Availability Installer Appliance

You can download the vCloud Availability Installer as an OVA file and deploy a new virtual machine. By performing an appliance redeployment, you lose all previously created registry records, password and trust information. For more information, see chapter Upgrading vCloud Availability for vCloud Director in the vCloud Availability for vCloud Director 1.0.1 Documentation.

Upgrading the vCloud Availability Administration Portal

You must upgrade the vCloud Availability Administration Portal host to version 1.0.1.4 to gain the capability to move replications between clustered datastores.

To upgrade the vCloud Availability Administration Portal host to version 1.0.1.4, you crate and configure a new appliance by using the vCloud Availability Installer appliance. For more information, see Create vCloud Availability Administration Portal Host and Configure vCloud Availability Administration Portal Host topics in the vCloud Availability for vCloud Director 1.0.1 Documentation.

Product Documentation

In addition to the current release notes, you can use the documentation set for vCloud Availability 1.0.1 that includes the following deliverables.

Resolved Issues

  • You cannot perform a storage migration to a cluster datastore by using the vCloud Availability Administration Portal as cluster datastores are not listed as destination candidates in the storage migration wizard

    In the vCloud Director API, the cluster datastore schema is different than the local datastore schema. The datastore field name is not provided for cluster datastores. The vCloud Availability Administration Portal does not account for this interface inconsistency and fails to list the cluster datastores as destination candidates.

    You can perform a storage migration from a cluster datastore to a local datastore, although the datastore name for the present replication is displayed empty in the vCloud Availability Administration Portal.

    This issue is fixed. Migration to and from cluster datastore by using the vCloud Availability Administration Portal is now supported. When performing a storage migration from or to a cluster, select the MOREF of the datastore.

  • The vcav hcs configure, vcav org *, and vcav org-vdc * commands may time out in large environments with hundreds of vCloud Director organizations

    The scripts pull the full record for each organization in vCloud Director. This can create an extensive delay in deployments where there are hundreds of organizations.

    This issue is fixed.

Known Issues

  • You receive an Invalid Payload error in the vCloud Availability Administration Portal, if you use the vCloud Availability Administration Portal to migrate a replication VM from a datastore, to which only the default, *(ANY), storage policy is applied, to а datastore which has a different storage policy applied

    When a tenant configures replication to cloud and selects the *(ANY) storage policy, all the replicated VMs are stored to all the shared datastores to which *(ANY) storage policy is applied. In this case, if you try to move the replications to a datastore to which a different storage policy is applied, the vCloud Availability Administration Portal returns the Invalid Payload error.

    This issue affects only datastores to which *(ANY) storage policy is applied. If a storage policy that is different than *(ANY) is applied to the datastore when replicating to-the-cloud, you do not receive the error and the Storage Migration operation completes successfully.

    Workaround: To work around this issue, create a new storage policy in your resource vCenter Server and apply the new policy to the datastore which you wanted to move a replication VM from. Attach the new storage policy to the PVDC in vCloud Director. It can take up to couple of minutes for the newly created storage policy to appear in vCloud Director. Once the synchronization is done, repeat the migration operation.

     

check-circle-line exclamation-circle-line close-line
Scroll to top icon