VMware vCloud Availability for vCloud Director 1.0.1 Release Notes

VMware vCloud Availability for vCloud Director 1.0.1 | 26 JAN 2017 | Build 4945120

Last updated: 10 OCT 2017

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

Localization

VMware vCloud Availability for vCloud Director 1.0.1 is available in English language.

What's New

vCloud Availability for vCloud Director provides disaster recovery and migration services from an on-premises vCenter to a service provider cloud. vCloud Availability for vCloud Director 1.0.1 delivers several key enhancements, including the all-new vCloud Availability for vCloud Director Portal, a migration workflow to enable easy transfer of vSphere VMs between on-premises environments and the cloud, and a rapid installer to help service providers get up and running with vCloud Availability services faster and to extend existing DR infrastructure.

With the new vCloud Availability for vCloud Director Portal, you can perform vCloud Availability for vCloud Director tasks and monitor the progress of running tasks.

Monitoring vCloud Availability for vCloud Director processes

  • Workloads health status.
  • Usage status of the DR-enabled VDC instances.
  • Task status for completed and ongoing tasks.
  • Progress indicator for ongoing tasks.

You can perform the following tasks by using the vCloud Availability for vCloud Director Portal

  • Failover workloads from on-premise to cloud sites.
  • Failback workloads from cloud to on-premise sites.
  • Failover Reverse workloads to synchronize data from cloud to on-premise sites.
  • Failback Reverse workloads to synchronize data from on-premise to cloud sites.
  • Test VM Replication.
  • Cleanup test artifacts after tests are completed.
  • Detach or Unprotect to remove VMs from vCloud Availability for vCloud Director solution.
vCloud Availability Installer 1.0.1 Appliance

Installing and configuring the vCloud Availability Installer appliance is the starting point for installation of all vCloud Availability products. The appliance is distributed as an OVA with all VMware binaries in place and ready to be used.

  • CLI app (vcav) script for installation and maintenance operations.
  • A Photon image for running Docker images.
  • Certificate management capabilities to easily register and connect components.
  • Validation of the components configuration during the installation and configuration process.
  • DCHP and Static IP Support with management of underlying IP Pool for the desired network and IP range.
  • Full Command and Registry-Based Model, flexible enough to support all vCloud Director deployment architectures.

Product Documentation

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

Upgrading vCloud Availability for vCloud Director

The active vSphere Replication components of vCloud Availability for vCloud Director 1.0.1 remain the same as in vCloud Availability for vCloud Director 1.0.0. You can upgrade to vCloud Availability for vCloud Director 1.0.1 by installing and configuring a vCloud Availability Installer appliance and a vCloud Availability for vCloud Director Portal host. You must also connect your existing vCloud Availability for vCloud Director components to your vCloud Availability Installer appliance. You can then deploy and configure new vCloud Availability for vCloud Director appliances using the vCloud Availability Installer appliance. For more information, see Upgrading vCloud Availability for vCloud Director.

Supported Browser Versions

The vCloud Availability for vCloud Director 1.0.1 is compatible with the following browsers.

  • Google Chrome 51.0 or later
  • Safari 9.1 or later
  • Mozilla Firefox 49 or later
  • Microsoft Edge 38 or later
  • Microsoft Internet Explorer 11 or later

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.

General

The issues in this section pertain to the vCloud Availability for vCloud Director solution.

  • Setting the storage lease for organizations results in replicated VMs being removed from vCloud Director web interface while replication remains valid

    After configuring replication for a tenant VM, the vCloud Availability for vCloud Director solution creates a vApp in the vCloud Director web interface. The vApp is a subject to all rules, including such created directly by the user. If the user configured a storage lease in the organization, the lease will be applied to the new vApp as well. The vCloud Director system will clean up the vApp at the end of that storage lease and apply the policy configured for the organization.

    Workaround: You have the following options to work around this issue.

    • Update the storage lease for each organization to "Never Expire" so the stopped vApps never expire. If you change this setting after vApps are created, you need to update each vApp, so it has the new policy to never expire.
    • Setup a process to track the expiration of all replicated VMs and renew them prior to their expiration.
    • Set the expiration policy to "Move to Expired Items". By using this option, you or the user can renew the lease for the vApp without required resynchronization.
  • The vSphere Replication Service may fail to start correctly if multiple vCloud Director cells are using the same Platform Service Controller

    The following error may occur if the vCenter Lookup Service includes multiple entries for vCloud Director endpoints.

    Caused by: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://192.168.10.10/api/sessions": java.security.cert.CertificateException: Certificate thumbprint mismatch; expected: 4e:fc:1c:6c:b4:30:4d:43:46:3d:7a:7c:e5:4e:27:c9:df:1f:be:27, but encountered: 65:AE:D0:CF:FF:E5:F4:98:7C:B5:B6:72:55:36:23:A1:F2:34:65:22; nested exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificate thumbprint mismatch; expected: 4e:fc:1c:6c:b4:30:4d:43:46:3d:7a:7c:e5:4e:27:c9:df:1f:be:27, but encountered: 65:AE:D0:CF:FF:E5:F4:98:7C:B5:B6:72:55:36:23:A1:F2:34:65:22

    Workaround: Using the same wildcard certificate for all vCloud Director instances. If you receive the error during vCloud Availability for vCloud Director configuration, check the DNS entry and the associated certificate match expectations. If the DNS entry and the associated certificate are valid, check the Lookup Service for multiple vCloud Director entries. Removing additional vCloud Director entries and restarting the hcs service allows you to work around the issue.

  • If you power on a placeholder vApp created by vCloud Availability for vCloud Director and later migrate the VM to the cloud, when you attempt to power on the migrated VM, the NIC is misconfigured and not connected. No communication with the VM is possible.

    When you configure a VM for to-the-cloud replication, vCloud Availability for vCloud Director creates a placeholder vApp containing a placeholder VM in the tenant's organization VDC. The placeholder vApp is managed by the vCloud Availability for vCloud Director solution and might not be used or modified until the source VM is migrated to the cloud provider site. An attempt to power on the placeholder vApp returns the following error:

    Failed to power on VM - The method is disabled by 'hms.cloud.service'.

    Despite the error message, an unwanted change is performed on the placeholder VM network card configuration. This change leads to a misconfiguration of the NIC when the VM is migrated and started.

    Workaround: None. To avoid this issue, do not attempt to power on placeholder vApps or VMs when configuring to-the-cloud replication.

  • Protecting VMs for a single tenant in two organization VDCs using the same vCloud Director and the same provider VDC results in a vCloud Tunneling Agent error and the VMs state changes to Not Active or Error.

    If you pair a single tenant to two different organization VDCs, the pairing and the connection are successful but when you configure a replication, the VMs from the second paired organization VDC enter a Not Active or Error state. The following error message might appear:

    Cannot create a secure tunnel for replication to the cloud. Check the status of the vCloud Tunneling Agent service.

    Workaround: None.

  • Protecting VMs for two tenants in a single organization VDC using the same vCloud Director and different provider VDCs results in a vCloud Tunneling Agent error or VMs changing state to Not Active or Error.

    If you pair two tenants to a single organization VDC, the pairing and the connection are successful but when you configure replication, the VMs from the second paired tenant might enter a Not Active or Error state, or the following error message might appear:

    Cannot create a secure tunnel for replication to the cloud. Check the status of the vCloud Tunneling Agent service.

    Workaround: None.

Installation and Configuration

The issues in this section are specific to the installation and configuration operations.

  • Certificates using a self-signed Intermediate Certificate Authority may result in an SSL Error during configuration

    You may receive the following error if you are using a self-signed Intermediate Certificate Authority certificate.

    bad handshake: Error([('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')],)

    Workaround: You can work around this error by adding -k option to the command and run it again. With this option you can use SSL and SSH connections without a certificate validation. The script displays warning messages, but the command completes.

  • Attempts to reconfigure vSphere Replication appliances returns an error message

    During the configuration of the vCloud Availability for vCloud Director solution, you run configure commands from the vCloud Availability Installer appliance. If you try to run the configure command on an appliance that is already configured, you receive the following error.

    ERROR - The host at VM-IP-Address is already configured

    Workaround: You can work around this error by adding --reconfigure option to the command and run it again. The command ignores previous configuration.

  • The RabbitMQ password cannot contain a dollar sign ($) for RabbitMQ versions earlier than 3.6.6

    When the RabbitMQ user password includes a dollar sign ($) the vcav script and vCloud Director APIs are unable to validate the results against earlier versions of RabbitMQ. You receive the following error message.

    The AMQP settings are not valid: [ 5a259ad4-2ad5-47aa-8a24-0e5d37c4009b ] Possibly caused by authentication failure - connection error; reason: java.io.EOFException

    Workaround: Assign a new password to the RabbitMQ user and proceed with configuration. Ensure the password does not include a dollar sign ($).

  • Configuring the vSphere Replication Cloud Service host fails with an error message

    vCloud Director, vSphere Replication Cloud Service host, and vCenter Server instances registered in vCloud Director must use the same PSC domain. If any of the instances uses different PSC domain, the vcav hcs configure command to configure the vSphere Replication Cloud Service host will fail with the following error message.

    Cannot complete login due to an incorrect user name or password.

    Workaround: Register all vCloud Director, vSphere Replication Cloud Service host, and vCenter Server instances registered in vCloud Director in the same PSC domain.

  • Creating a new vCloud Availability for vCloud Director appliance with the vCloud Availability Installer appliance may return an error

    Using the vCloud Availability Installer appliance to create new appliances, you run the vcav [new appliance] create command. You may receive the following error during such operations.

    ERROR - (vim.fault.InvalidGuestLogin) { dynamicType = , dynamicProperty = (vmodl.DynamicProperty) [], msg = 'Failed to authenticate with the guest operating system using the supplied credentials.', faultCause = , faultMessage = (vmodl.LocalizableMessage) []}

    As a result the ssh trust between the vCloud Availability Installer appliance and the newly deployed appliance is not created. You are not able to configure the new appliance.

    Workaround: Run the same vcav [new appliance] create command and add the --overwrite option. This command deletes the deployed appliance and creates a completely new one.

  • Configuration verification may return an error

    Using the vCloud Availability Installer appliance to verify configuration is completed, you run the vcav [appliance alias] check command. You may receive the following error during such operations.

    ERROR - Unable to find the ovf environment.

    Log in to the terminal of the affected appliance and run ovfenv command. If the command returns Unable to find the ovf environment error, you need to reload the runtime OVF environment.

    Workaround: Power off the affected VM, power it back on, and run the command again.

  • Running vcav vcd [operation] commands or commands that contain the vcd-address argument on your vCloud Availability Installer may return the following error

    ERROR - Unable to login to VCD VCD-IP-Address

    This error occurs because the vCloud Director API requires that all API login requests include an organization name within the credentials provided. Login requests will fail if the organization name is missing.

    Workaround: Administrative users must use System organization. Use the vCloud Director user interface to confirm the credentials you are using are correct and update the --vcd-user argument in the command or the registry file to include @System in the vCloud Director API user.

  • Using the default Cassandra 2.2 docker container fails when running vcav cassandra create, vcav trust add and vcav cassandra register commands on the vCloud Availability Installer appliance.

    The Cassandra 2.2.9 docker container is not compatible with the vcav script.

    Workaround: Use Cassandra 2.2.8 docker container by adding the --docker-image=cassandra:2.2.8 argument in the vcav cassandra create command, as shown in the following example.

    # vcav cassandra create \
    --docker-address=$DOCKER01_ADDRESS \
    --docker-image=cassandra:2.2.8 \
    --container-name=vcav-cass01 \
    --cassandra-port=9042

vCloud Availability for vCloud Director Portal

The issues in this section are specific to the vCloud Availability for vCloud Director Portal.

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

    This performance problem is caused by API calls to the vCloud Director instance. The API calls are required to set up cached information for the user sessions.

    Workaround: You have the following two options to work around this issue.

    • Increase the compute and memory resources allocated to the vSphere Replication Management Server.
    • Deploy additional vSphere Replication Management Server instances and distribute workloads across multiple VDC instances attached to different vSphere Replication Management Server instances.
  • Running a Power On task for a peer VM from the Reversed tab sometimes results in an error status for the task on the Tasks tab

    Workaround: None.

  • Running a Power Off task for a peer VM from the Reversed tab is sometimes reported as a FailbackPowerOn task from a different session on the Tasks tab

    Workaround: None.

  • Running a Power Off task for a reversed VM does not power off the VM.

    If you run a Power Off task for a reversed VM, the VM appears as Powered On in the vCloud Director Web console, although in the vCloud Availability for vCloud Director Portal it is in a Powered Off state. As a result, you are not able to perform a Failback Reverse task for the same VM.

    Workaround: After the Power Off task completes in the vCloud Availability for vCloud Director Portal, power off the VM using the vCloud Director Web console.

Documentation Issues

  • NEW The vCloud Availability for vCloud Director 1.0.1 Administration guide is updated with new information.
  • The vCloud Availability for vCloud Director 1.0.1 Documentation Center now includes an extended and reorganized vCloud API Schema Reference. For more information, see the vCloud API Schema Reference.

    For a full list of the latest documentation enhancements, see Updated Information.