Load Balancer Cloud is not in ready state when enabling load balancer for Edge Gateway xxxxxxxx with
Tier-1 xxxxxxxxxxxxxxxxxxxxxxxxx. Cloud has state CLOUD_STATE_PLACEMENT_READY and reason: .- VrfContext is not ready yet for Edge Gateway.
/opt/vmware/vcloud-director/logs/vcloud-container-debug.log
, you see messages similar to:com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Load Balancer Cloud is not in ready state when enabling load balancer for Edge Gateway
. Cloud has state CLOUD_STATE_PLACEMENT_READY and reason: .xxxxxxxx with
Tier-1 xxxxxxxxxxxxxxxxxxxxxxxxx
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.waitForCloudReadyStateAndReturnVrfContext(NsxTEdgeLoadBalancer.java:570)
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.registerGatewayAndLoadBalancerServiceNetworkOnNsxAlbCloud(NsxTEdgeLoadBalancer.java:546)
Caused by: com.vmware.vcloud.common.network.NsxAlbApiException: VrfContext is not ready yet for Edge Gateway
xxxxxxxx with
Tier-1 xxxxxxxxxxxxxxxxxxxxxxxxx
.
NSX ALB -> Operations -> All Events
, you would see the following:error_message: "Cannot delete, object is referred by: ['Pool VCD-LoadBalancer-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx']"
VMware Cloud Director 10.x
VMware Avi Load Balancer
This issue occurs when the pool is not being used but still referred by a vrf context because of which the Load balancer fails to enable on the edge gateway from the VCD UI.