check-circle-line exclamation-circle-line close-line

VMware vCloud Availability for vCloud Director 2.0.1 Release Notes

VMware vCloud Availability for vCloud Director 2.0.1 | 22 FEB 2017 | Build 7826078

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

vCloud Availability 2.0.1 delivers the following enhancements:

  • Bug fixes described in the Resolved Issues section.
  • The following documentation improvements:
    • Introduced vCloud Availability as the new short name for the vCloud Availability for vCloud Director solution.
    • The name of the vCloud Availability for vCloud Director Portal changes to vCloud Availability Portal.
    • The name of the vCloud Availability for vCloud Director Service Manager Portal changes to vCloud Availability Administration Portal.
    • Updated vCloud Availability for vCloud Director 2.0 Installation and Configuration Guide. For a list of documentation enhancements, see Updated Information.
    • Updated vCloud Availability for vCloud Director 2.0 Administration Guide. For a list of documentation enhancements, see Updated Information.
    • Updated vCloud Availability for vCloud Director 2.0 Upgrade Guide. For a list of documentation enhancements, see Updated Information

Supported Browsers

The vCloud Availability Portal 2.0.1 is tested against the following Web browser versions. You can use older versions.

Windows 10

  • Microsoft Internet Explorer 11.1944.14393.0
  • Microsoft Edge 38.14393.1066.0
  • Mozilla Firefox 57.0.3 (64-bit)
  • Google Chrome 63.0.3239.132 (Official Build) (64-bit)

macOS Sierra 10.12.6

  • Mozilla Firefox 57.0.3 (64-bit)
  • Google Chrome 63.0.3239.132 (Official Build) (64-bit)

CentOS 7.3

  • Mozilla Firefox 57.0.3 (64-bit)
  • Google Chrome 63.0.3239.132 (Official Build) (64-bit)

The vCloud Availability Administration Portal 2.0.1 is tested against the following Web browser versions. You can use older versions.

Windows 10

  • Microsoft Edge 38.14393.1066.0
  • Mozilla Firefox 57.0.3 (64-bit)
  • Google Chrome 63.0.3239.132 (Official Build) (64-bit)

macOS Sierra 10.12.6

  • Mozilla Firefox 57.0.3 (64-bit)
  • Google Chrome 63.0.3239.132 (Official Build) (64-bit)

CentOS 7.3

  • Mozilla Firefox 57.0.3 (64-bit)
  • Google Chrome 63.0.3239.132 (Official Build) (64-bit)

Upgrade

To upgrade your vCloud Availability environment to version 2.0.1, you upgrade the vSphere Replication components and redeploy the vCloud Availability Installer Appliance, the vCloud Availability Portal, and the vCloud Availability Administration Portal. For more information, see the vCloud Availability for vCloud Director 2.0 Upgrade Guide.

Product Documentation

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

Resolved Issues

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

  • If multiple network profiles are configured in vSphere, deploying vCloud Availability for vCloud Director components may fail

    When deploying a vCloud Availability, if the first network profile for the IP that will be assigned does not have all parameters specified, the vcav script returns the following error:

    The IP Pool Network-Profile-Name definition in DC-Name for IP-Address does not have any DNS servers

    The script does not attempt to use other network profiles.

    This issue is fixed.

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

  • The vCloud Availability Administration Portal stops updating report data

    You must manually regenerate reports to reflect latest changes. Restarting the vCloud Availability Administration Portal does not resolve the issue and you get the following warning message in the homepage:

    Instant data updates are not available now due to an error in messaging system. Please make sure the server is properly configured.

    The vCloud Availability Administration Portal does not acknowledge AMQP messages from vCloud Director.  This leads to the AMQP message queue for the vCloud Availability Administration Portal growing significantly. As a result, RabbitMQ becomes unstable and starts failing to serve requests for vCloud Director.

    This issue is fixed.

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

    This issue is fixed.

Known Issues

  • Moving replica files to a new datastore does not work for healthy replications

    When you configure an on-premise to cloud replication by using an existing base disk, which has parent disks, then you cannot move replica files to another datastore. This can happen when you use seeding to vCloud Director and the seed VM has snapshots, or needs consolidation. This issue also affects the reverse operations. For reverse operations to work, you must first manually consolidate the VM in the destination site.

    Workaround: To work around this issue, perform a planned migration or a failover, then consolidate the recovered VM's disks, remove the replication object, and configure a new replication.

  • System administrators cannot use an existing vCenter Single Sign-On configuration to authenticate against vCloud Director

    Federation for the System organization changed in vCloud Director 9.x version. The System organization can now use any SAML identity provider, not just the vCenter Single Sign-On service. Existing federation settings for the System organization are no longer valid and are deleted during upgrade from vCloud Director 8.x.

    Workaround: To work around this issue, re-register your organization with your SAML identity provider. For more information, see Enable Your Organization to Use a SAML Identity Provider in the vCloud Director documentation.

  • When you configure a replication, you might receive the following error:

    Cannot create a secure tunnel for replication to the cloud. Check the status of the vCloud Tunneling Agent service. Exception details: 'Task failed. Failed to create to-the-cloud tunnel. Cannot resolve destination ID '52ed8c33-9538-808d-43f8-da46f62717f0': timed out(10s) tunneling app'.

    When you are using vCloud Director 9.0.0.2 with an earlier version of vCloud Availability, and decide to upgrade to vCloud Availability 2.0.1 by removing all appliances and unconfiguring the solution completely, the new vCloud Availability 2.0.1 instance installs successfully. However, when you map a tenant to a VDC and try to configure a replication, you receive the aforementioned error.

    Workaround: To work around this issue, restart the vCloud Director cell, the cloud proxy, HBR, HMS, and HCS services.