vCloud Availability 3.0.4 | 17 OCT 2019 | Build 14869413
What's in the Release NotesThe release notes cover the following topics:
vCloud Availability 3.0.4 includes a number of resolved issues and updates of third-party libraries providing security fixes.
You upgrade vCloud Availability from version 3.0 to version 3.0.4 by using the command-line interface of the vCloud Availability appliance.
You can perform an in-place upgrade directly from either vCloud Availability 3.0, vCloud Availability 3.0.1, vCloud Availability 3.0.2, or from vCloud Availability 3.0.3.
For more information about upgrading vCloud Availability in the cloud, see Upgrading vCloud Availability. For upgrading the on-premises vCloud Availability appliance, see Upgrading VMware vCloud Availability On-Premises.
- The network settings for on-premises to cloud replications cannot be changed
For on-premises to cloud replications, in the Network Settings window you receive an
Unable to connect to vCenter 'undefined'message. As a result you cannot change the network settings for on-premises to cloud replications.
- In the same window, enabling the tunnel configuration followed by disabling displays an error message
In the Tunneling Settings window, if you enable, then disable the tunnel and click Apply, you receive an
Operation aborted due to an unexpected errormessage.
- vCloud Availability 3.0.x cannot operate if the service provider access to the legacy API endpoint is disabled in vCloud Director 10
If you disable the service provider access to the
/api/sessionsAPI endpoint in vCloud Director 10, you cannot log in to vCloud Availability with service provider credentials or organization administrator vCloud Director credentials, you cannot protect or migrate vApps or virtual machines, and in vCloud Director you cannot access the vCloud Availability Plug-in.
1. Log in or SSH as root to the OS of any of the vCloud Director cells.
2. Enable the provider access to the
/api/sessionsAPI endpoint, use the cell management tool and run the following command:
./cell-management-tool manage-config -n vcloud.api.legacy.nonprovideronly -v false
- In a new deployment, the Update repository displays an error message
After you deploy an appliance, on the Configuration page under Version, for Update repository you see
Failed to retrieve update repo.
1. On the Configuration page, next to Update repository click Edit.
2. In the Update Repository window, select either Use Default Repository, or Use CDROM Updates, or Use Specified Repository and click Apply.
- Several days after upgrading to 3.0.3 or 3.0.4, the automatic replications sync stops progressing
After upgrading to vCloud Availability 3.0.3 or to vCloud Availability 3.0.4, in a few days the automatic synchronization of replications ceases to progress. The synchronization task remains as a random percent complete, for example at 28%. This issue prevents new instances from being created and causes RPO violations.
1. Connect to the vCloud Replicator instance by using a Secure Shell (SSH) client.
a. Open an SSH connection to the Replicator-IP-Address.
b. Log in as the root user.
2. Add the following configuration property.
echo “TRAFFIC_ACCOUNTING=false” >> /opt/vmware/h4/lwdproxy/conf/lwdproxy.properties
3. Restart the lwdproxy service.
systemctl restart lwdproxy
4. Log in to the vCloud Availability Portal as a tenant or as a service provider.
5. To verify that the replications synchronization is operational, select a replication and click the Sync button.
6. Repeat this procedure for all vCloud Availability Replicator instances.
- Opening the network settings for some vApps or virtual machines may show an error message
For the cloud to cloud replications, when you select a vApp or a virtual machine and click Networks, in some cases you may see a
Cannot read property 'nics' of nullerror message.
Workaround: Upgrade to vCloud Availability 3.0.5