VMware vCloud Availability for vCloud Director 2.0 Release Notes

|

VMware vCloud Availability for vCloud Director 2.0 | 19 OCT 2017 | Build 6918495

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

What's New

vCloud Availability for vCloud Director 2.0 delivers the following key enhancements: 

  • vSphere 6.5 Support: Added support for vSphere 6.5 on the service provider side. The supported vSphere versions on the tenant side remain unchanged. For more interoperability and compatibility information about vCloud Availability for vCloud Director, see the Interoperability Pages for vCloud Availability for vCloud Director 2.0.

  • 5-minutes Recovery Point Objective (RPO): vCloud Availability for vCloud Director 2.0 delivers an enhanced RPO support of 5-minutes compared to the previously supported RPO of 15 minutes.

  • Enhancements to vCloud Availability for vCloud Director Service Manager Portal: The Service Manager Portal, introduced in the vCloud Availability for vCloud Director 1.0.1.2 release, allows service providers to monitor and manage their DR environments. The current release includes usability and performance enhancements to improve the response time on the Inventory page and a new Tenant Impersonation feature. The new feature allows service providers to act as tenant users. Using the Tenant Impersonation feature, service providers can filter tenant organizations and perform DR operations using a tenant role, the same way a tenant user would.

  • Installer Simplification: Service providers can now install vCloud Availability for vCloud Director using one single command with an all-in-one appliance. All the vCloud Availability for vCloud Director components are now bundled into a single appliance to simplify the installation process.

  • Seamless upgrade: You can now upgrade to vCloud Availability for vCloud Director 2.0 from 1.X versions with no impact to protected virtual machines and existing replications. 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 for vCloud Director 2.0 that includes the following deliverables.

Resolved Issues

The following issues have been fixed in this release.
  • The vCloud Availability for vCloud Director Portal home page takes too long to load when one or more vSphere Replication Servers are offline

    This issue is fixed.

  • Replicated VMs have guest customization enabled if the target vCloud Director is version 9.0

    As a result, such VMs receive a new identity when they are powered on. You may observe this behavior for Windows versions,for which the cloud system administrator has not provided appropriate Microsoft Sysprep files.
    This issue is fixed with vCloud Director version 9.0.0.1.

  • The vCloud Availability for vCloud Director Portal may experience slow initialization on login when multiple tenant accounts access the portal simultaneously

    This issue is fixed.

Known Issues

The following known issues have been discovered through rigorous testing and will help you understand some behavior you might encounter in this release.

The known issues are grouped as follows.

Installation and Configuration
  • Installation fails with the following error message

    Cassandra cass.0 () took too long to start after importing the certificate for HCS hcs.1 ()

    The Cassandra server takes too long to become available on the network. Possible reason for the issue is a Cassandra cluster initialization.

    Workaround: To work around this issue, do the following:

    • For manual deployment, run the same command again. 
    • For autmated deployment, run vcav resume.
  • Configuring a vSphere Replication Server fails with the following error message

    The VR server for HBR-address is not connected

    The cause for this issue is that previously configured instances of vSphere Replication Server are not properly removed.

    Workaround: To work around this issue, do the following:

    1. Run the vcav hbr list --vcd=vCD-Registry-Name command.
    2. Identify all vSphere Replication Server instances that use the same address as the vSphere Replication Server that you are trying to configure.
    3. Unregister all conflicting entries by running the vcav hbr unregister --vcd=vCD-Registry-Name --hbr-uuid=UUID-of-the-conflicting-entry command.
    4. Attempt to configure the vSphere Replication Server again.
vCloud Availability for vCloud Director Service Manager Portal

 

  • Using Microsoft Edge or Microsoft Internet Explorer, you cannot download report data as a CVS file

    This issue is caused by compatibility problems between the Microsoft Internet Explorer and Microsoft Edge, and the JavaScript version that vCloud Availability of vCloud Director Service Manager Portal uses. 

    Workaround: To work around this issue, use a supported version of Google Chrome or Mozilla Firefox to download the report data.

  • If you use non-alphanumeric characters in the filter search box, the vCloud Availability for vCloud Director Service Manager Portal might become unresponsive

    When you use the filter search box, if you enter an invalid regular expression pattern, the Service Manager Portal cannot process the inquiry and might stop responding.

     Workaround: To work around the issue, refresh the page and avoid using non-alphanumeric characters when using the filter search box.

  • Using Microsoft Edge, when you open the Replication table view, the time format in the Transfer Start Time is displayed incorrectly

    This issue is caused by compatibility problems between Microsoft Edge and the JavaScript version that vCloud Availability of vCloud Director Service Manager Portal uses. 

    Workaround: To work around this issue, use a supported version of Google Chrome or Mozilla Firefox to download the report data.

Other
  • Running vcav hcs configure returns an error if there are existing solution users already in the PSC

     

    There was an issue creating the HCS solution user: 
    Did not delete pre-existing solution user with the same certificate as ours due to: com.vmware.jvsl.sso.SsoException: 
    com.vmware.jvsl.sso.SsoException: 
    com.vmware.vim.sso.client.exception.AuthenticationFailedException : 
    Provided credentials are not valid.

     

    Workaround: To work around this issue, update the vSphere Replication Cloud Service Host Certificate and run the vcav hcs configure​ command again. For more information, see Update the vSphere Replication Cloud Service Host Certificate.

  • After you fail back a reversed workload, if you try to power on the VM by using an API call, you receive an error for the status of the task

    To power on a VM after a failback operation, you use the vr/failbackreplications/{replication_id}/action/powerOnVm API call. If VMware Tools is not installed on the target VM, the operation fails.

    The issue affects only the vr/failbackreplications/{replication_id}/action/powerOnVm API call.

    Workaround: It is safe to ignore this error. Although the status of the task is failed, the VM is powered on successfully.

  • The vcav script times out when attempting to update the Cassandra server to trust a vSphere Replication Cloud Service host

    Some Cassandra installations do not respond to service stop or systemctl stop commands because of a missing PID file.

    Workaround: To work around this issue, do the following:

    1. Run the following command on each Cassandra server to create a PID file.
      mkdir -p /var/run/cassandra; chown -R cassandra:cassandra /var/run/cassandra
    2. Manually stop and restart the Cassandra process.
    3. Make sure that a PID file exists in /var/run/cassandra.
  • 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.

    Workaround: None.