Protection and Recovery Proxy Deployment Stuck in "In Progress" State due to IP Pool Exhaustion

Products

• VMware Live Recovery

Issue/Introduction

When attempting to redeploy or configure a Protection and Recovery Proxy appliance in VCF Automation, the task remains stuck in an "In Progress" state indefinitely.

The following symptoms may be observed:

• UI Error: "Failed to check local Data Protection Service connectivity" in the VCF Automation interface under Protection and Recovery > Paired vCenters.

• Service Status: Running kubectl get services -A | grep dr on the Supervisor cluster shows the dr-loadbalancer service in a Pending state.

• Load Balancer Status:

kubectl get service dr-loadbalancer -n svc-supervisor-management-proxy-kct99

NAME              TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)            AGE
dr-loadbalancer   LoadBalancer   172.##.##.##0  <pending>     10095:31363/TCP    15d

• AVI Kubernetes Operator logs for manager may show the events as below.

"vsvip_cloud_config_cksum":"3346822388"} returned err {"code":0,"message":"map[error:Failure to Allocate VIP in subnet kube-system_6i3i9_AVISEPARATOR_PUBLIC for cloud CLOUD_NSXT - error IpAddressBlocks path=[/infra/ip-blocks/a68531f4-32f7-439e-9ce2-####,/infra/ip-blocks/5f6a1768-347e-46b5-b915-####,/infra/ip-blocks/62a8aa6a-110a-458e-a49d-####] do not have spare capacity to allocate CIDR of size 1.]","Verb":"POST","Url":"https://1##.##.##.##//api/vsvip","HttpStatusCode":400} with response null

Environment

• Protection and Recovery 9.1

• VMware Cloud Foundation Automation 9.1

Cause

 Insufficient IP addresses in the NSX IP Address Pool prevent the Avi Kubernetes Operator (AKO) from allocating a Virtual IP (VIP) for the load balancer.

Resolution

To resolve this issue, you must increase the capacity of the IP Address Pool in NSX.

Step 1: Expand the NSX IP Address Pool

1. Log into the NSX Manager UI.
2. Navigate to Networking > IP Address Pools.
3. Locate the pool used for the Supervisor/VCF Automation services.
4. Click Edit on the pool.
5. Add a new Subnet or expand the existing IP Range to provide additional available addresses.
6. Click Save.

Step 2: Verify Recovery

Once the IP pool has sufficient capacity:

1. AKO will automatically detect the available IPs and assign a VIP to the dr-loadbalancer.
2. Verify the status again: kubectl get service dr-loadbalancer -n svc-supervisor-management-proxy-kct99. The EXTERNAL-IP should now show a valid IP address.
3. The Protection and Recovery Proxy deployment should now transition from "In Progress" to "Success".