VMware Cloud Director Availability™ 184.108.40.206 | 25 NOV 2021 | Build 18964982 (Product version: 220.127.116.1131795-5f4fbe1b93)
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
VMware Cloud Director Availability 18.104.22.168 includes only the following important resolved Issues.
VMware Cloud Director Availability 22.214.171.124 supports an in-place upgrade directly from versions 126.96.36.199, 188.8.131.52, 4.1.1, 4.2, and 4.2.1. For more information, see Upgrading in the Cloud and Upgrading On-Premises.
- Tenants cannot start new outgoing replications by using multisite authentication to 4.2.x sites using VMware Cloud Director 10.2 or later
Starting new outgoing protection or migration as a tenant when using multisite authentication to extend the session to destination sites using VMware Cloud Director Availability 4.2.x and VMware Cloud Director 10.2 or later, completes the task with an error message
The provided credentials are not valid. This issue does not affect the service providers.
- Error when using the uplink IP address of the Edge Gateway when creating the server L2 VPN session
Attempting to use the uplink IP address of the NSX-V Edge Gateway when creating the server L2 VPN session results in the following error message.
IP Address is not within allowed range(s)
- After re-balancing replications, performing a test failover, and other management operations remain indefinitely at 1-2% progress
To prevent the replication from being corrupted, performing management operations locks the replication before performing any changes to it.
Re-balancing replications detaches the replication from one Replicator Service instance and attaches it to another instance. In case of an error, this replication lock does not get released.
As a result, all subsequent management operations, for example, pause, resume, test failover, and others fail with the following error message.
Lock acquisition timed out for object: H4-bc6f965c-0be4-4325-9c87-a666ba418e44.
To verify that this caused the issue, open an SSH connection to the Cloud Replication Management Appliance.
psql -U h4postgres -d h4manager -c "select * from task where resource_id = 'H4-bc6f965c-0be4-4325-9c87-a666ba418e44' and state = 'RUNNING' and type = 'switchDestinationReplication';"
/opt/vmware/h4/manager/log/manager.logor in one of the log archives verify that the following ERROR message is present.
Re-attach of replication H4-bc6f965c-0be4-4325-9c87-a666ba418e44 to replicator 1ef53db8-fe7d-4cca-864e-012611273c25 failed.