VMware vCloud Availability for vCloud Director 1.0.1.3 Release Notes

VMware vCloud Availability for vCloud Director 1.0.1.3 | 17 AUG 2017 | Build 6293411 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
• Upgrade
• Product Documentation
• Resolved Issues
• Known Issues

What's New

vCloud Availability 1.0.1.3 delivers new bug fixes described in the Resolved Issues section and the following enhancements of the vCloud Availability Installer appliance scripts:

• The vcav cassandra import-hcs-certificate script can now determine if Cassandra is hosted on a system using systemd. As a result, the script formats the version of the command for stopping, starting, and getting the status of the Cassandra service regardless of the system host.
• Тhe vcav cassandra import-hcs-certificate script can execute a discovery of the keytool command if it is not included in the user's path.
• Enhanced vcav hbr configure script to support configuring a vSphere Replication Server in a topology where the vSphere Replication server cannot reach some of the ESXi hosts managed by a vCenter Server, and the configuration takes long time to factor in the connection timeputs.

Upgrade

To upgrade your vCloud Availability solution to version 1.0.1.3, you must upgrade the vCloud Availability Installer appliance. All other components remain unchanged.

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 in the vCloud Availability for vCloud Director 1.0.1 Documentation Center.

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.

• vCloud Availability for vCloud Director 1.0.1 Documentation
• Interoperability Pages for vCloud Availability for vCloud Director 1.0.1
• NEW The vCloud Availability for vCloud Director 1.0.1 Day 2 Operations Guide is extended to cover Password Management and Certificate Management. For a list of the documentation enhancements, see Updated Information.

Resolved Issues

The following issues are resolved in this release of vCloud Availability.

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

  is now resolved

• Creating a new vCloud Availability 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.

  is now resolved.

• Running vcav scripts on the vCloud Availability Installer appliance returns a vCloud Director authentication error

  If you run vcav login vcd command and then run another vcav command without specifying all required arguments, the operation fails, and you receive the following error:

  ERROR - Unable to write password for --vcd-password-file to remote server

  is now resolved.

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

  Workaround: None.