Unable to synchronize existing On-Premises to Cloud replications after renewing the Cloud Director Availability On-Premises Appliance certificate

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• In the Cloud Director Availability Portal, On-Premises to Cloud replications experience RPO violations.
• On-Premises to Cloud replications show an overall health of yellow but a green replication state.
• Creating new replications from the same On-Premises site complete successfully with an overall health of green.
• In /opt/vmware/h4/lwdproxy/log/lwdproxy.log on the Cloud Replicator Appliance, you see entries similar to:

2020-10-01 12:19:33,749 WARN [Worker-3-1] c.v.h.p.a.LwdAuthorizer [LwdAuthorizer.java:49] Access denied for client 5A:0A:F4:4F:00:9F:09:E9:5A:AE:E1:43:##:##:##:##:##:##:68:61:D7:BC:8C:07:72:32:14:FC:33:65:B2:F1:F6:41:CF:88:CC:CD:13:88:8D:B8:32:B5:8A:34:BA:3F:0C:A7:91:76:6A:EB:2D:81:0D:62:B4:E2:FB:BF:2C:41 over GID:H4-########-####-####-####-##########4f
2020-10-01 12:19:33,749 WARN [Worker-3-1] c.v.h.p.h.InitSessionHandler [InitSessionHandler.java:80] Access denied for LWDS peer 5A:0A:F4:4F:00:9F:09:E9:5A:AE:E1:43:##:##:##:##:##:##:68:61:D7:BC:8C:07:72:32:14:FC:33:65:B2:F1:F6:41:CF:88:CC:CD:13:88:8D:B8:32:B5:8A:34:BA:3F:0C:A7:91:76:6A:EB:2D:81:0D:62:B4:E2:FB:BF:2C:41 over group H4-########-####-####-####-##########4f
2020-10-01 12:19:33,749 WARN [Worker-3-1] c.v.h.p.u.TrafficCounter [TrafficCounter.java:65] Unknown counter: 005056fffe8bbff8-0000663c-000011fa-481ba2b2708ecad4-92229ed2

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Director Availability 4.x

Cause

This issue occurs when the lightweight delta service certificate on the Cloud Director Availability On-Premises Appliance is regenerated but this change doesn't get updated on the cloud site for existing replications.

Resolution

This is a known issue affecting Cloud Director Availability 4.x.

Currently there is no resolution.

Workaround:
To work around this issue you need to reconfigure affected replications. To do this in the least disruptive way, you can perform the following steps.

1. Log into the Cloud Director Availability Portal.
2. Select an affected replication.
3. Click All actions.
4. Under Settings, click Replication settings.
5. Toggle the Compress replication traffic option.
6. Click Apply.
7. Click All actions again.
8. Under Settings, click Replication settings.
9. Toggle the Compress replication traffic option back to its original setting.
10. Click Apply.