Unable to add IPv6 Service Network to Edge Gateway Load Balancer in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

1. When adding IPv6 Service Network Specification to an edge gateway you have the error below:
   
   [xxxx-xxxx-xxxx-xxxx-xxxx ] Tier1 '/infra/tier-1s/xxxx-xxxx-xxxx-xxxx-xxxx' cannot be deleted as Virtualservice 'VCD-LoadBalancer-xxxx-xxxx-xxxx-xxxx-xxxx' associated with it.


2. On opt/vmware/vcloud-director/logs/vcloud-container-debug.log you have entry similar below:
   
   YYY-MM-DD TIME       DEBUG        opt/vmware/vcloud-director/logs/vcloud-container-debug.log        task-service-activity-pool-1107 | CJob                           | updateFailedJob(com.vmware.vcloud.common.network.NsxAlbApiException) with locale=en_US | requestId=xxxx-xxxx-xxxx-xxxx-xxxx,request=PUT https://vcloud.example.com/cloudapi/1.0.0/edgeGateways/urn:vcloud:gateway:xxxx-xxxx-xxxx-xxxx-xxxx/loadBalancer,requestTime=1718363496452,remoteAddress=##.##.##.##:52196,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/json;version 39.0.0-alpha vcd=xxxx-xxxx-xxxx-xxxx-xxxx,task=xxxx-xxxx-xxxx-xxxx-xxxx activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:xxxx-xxxx-xxxx-xxxx-xxxx)
com.vmware.vcloud.common.network.NsxAlbApiException: Tier1 '/infra/tier-1s/xxxx-xxxx-xxxx-xxxx-xxxx' cannot be deleted as Virtualservice 'VIRTUAL_SERVICE_NAME' associated with it.
at com.vmware.vcloud.fabric.net.nsxalb.NsxAlbRestTemplateErrorHandler.handleError(NsxAlbRestTemplateErrorHandler.java:45)
...
at com.vmware.vcloud.networking.model.nsxalbresource.NsxAlbCloudResource.updateCloud(NsxAlbCloudResource.java:63)
at com.vmware.vcloud.networking.model.loadbalancer.NsxAlbLoadBalancerCloud.unRegisterLoadBalancerNetworkWithCloud(NsxAlbLoadBalancerCloud.java:354)
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.lambda$unRegisterGatewayAndSegmentOnNsxAlbCloud$4(NsxTEdgeLoadBalancer.java:597)
...
at com.vmware.vcloud.networking.model.loadbalancer.NsxAlbLoadBalancerCloud.invokeNsxAlbCloudUpdateWithRetries(NsxAlbLoadBalancerCloud.java:464)
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.unRegisterGatewayAndSegmentOnNsxAlbCloud(NsxTEdgeLoadBalancer.java:596)
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.updateNsxAlbAndNsxToDisableLoadBalancer(NsxTEdgeLoadBalancer.java:679)
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.disableLoadBalancing(NsxTEdgeLoadBalancer.java:666)
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.enableLoadBalancing(NsxTEdgeLoadBalancer.java:530)
at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.updateLoadBalancerConfig(NsxTEdgeLoadBalancer.java:455)
at com.vmware.vcloud.networking.services.handlerproxy.activity.edges.EdgeGatewayLoadBalancerActivity.updateLoadBalancerConfig(EdgeGatewayLoadBalancerActivity.java:26)
at com.vmware.vcloud.networking.services.handlerproxy.activity.CloudApiRunnableActivity.execute(CloudApiRunnableActivity.java:80)
at com.vmware.vcloud.networking.services.handlerproxy.activity.CloudApiRunnableActivity$ExecuteServiceMethod.invoke(CloudApiRunnableActivity.java:58)
...

 

Environment

VMware Cloud Director 10.5.x

Cause

The issue is related to stale entries. In AVI, the tier 1 gateway is already registered with a different stale network segment in NSXT Cloud named causing the failure in updating the IPv6 service network.

Resolution

Check for possible stale LB network segment in NSXT for tier 1 gateway and also check the registered data segment networks in the cloud in AVI. 
You might need to delete the obsolete mapping of Tier 1 and stale network segment in the cloud from AVI as well NSXT.