Error: "VrfContext is not ready yet for Edge Gateway <EDGE_NAME> with Tier-1 <EDGE_ID>" when attempting to enable Load Balancer Transparent Mode on an Edge Gateway
search cancel

Error: "VrfContext is not ready yet for Edge Gateway <EDGE_NAME> with Tier-1 <EDGE_ID>" when attempting to enable Load Balancer Transparent Mode on an Edge Gateway

book

Article ID: 393391

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

 

  • Cannot activate Transparent Mode under Edge Gateways > Edge Name > Load Balancer > General Settings in the Cloud Director Provider or Tenant Portals.
  • Task fails in the Cloud Director UI with an error of the form:

    Tier1 '/infra/tier-1s/########-####-####-####-############' cannot be deleted as Virtualservice 'VCD-LoadBalancer-########-####-####-####-############-<virtual_service_name>' associated with it" when attempting to enable Load Balancer Transparent Mode on an Edge Gateway.

  • The /opt/vmware/vcloud-director/logs/vcloud-container-debug.log on the Cloud Director Cells show an error of the form:

    <TIMESTAMP> | WARN     | task-service-activity-pool-### | NsxTEdgeLoadBalancer           | VrfContext is not ready for Edge Gateway <EDGE_NAME> with Tier-1 <EDGE_ID>. Cloud has state CLOUD_STATE_PLACEMENT_READY and reason: . Waited ### seconds. | requestId=########-####-####-####-############,request=PUT https://<VCD_ADDRESS>/cloudapi/1.0.0/edgeGateways/urn:vcloud:gateway:<EDGE_ID>/loadBalancer,requestTime=<REQUEST_TIME>,remoteAddress=#.#.#.#:#####,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/201...,accept=application/json;version 40.0.0-alpha vcd=########-####-####-####-############,task=########-####-####-####-############ activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-############)
    com.vmware.vcloud.common.network.NsxAlbApiException: VrfContext is not ready for Edge Gateway <EDGE_NAME> with Tier-1 <EDGE_ID>.
            at com.vmware.vcloud.networking.model.edge.nsxt.services.loadbalancer.NsxTEdgeLoadBalancer.getVrfContextUuid(NsxTEdgeLoadBalancer.java:748)

 

Environment

  • VMware Cloud Director 10.6.x
  • VMware Cloud Director 10.5.x
  • VMware Avi Load Balancer

Cause

This issue occurs if the VRF Context name in Avi Load Balancer is not correct for the Edge Gateway being modified in Cloud Director.

For example if the Edge Gateway is renamed in the Cloud Director UI, then this name change may not be propagated down to the VRF Context in Avi Load Balancer.

Resolution

To resolve the issue, ensure that the name of the VRF Context in Avi Load Balancer associated with the Cloud Director Edge is in the correct format.
The name of the VRF Context must take the from <EDGE_NAME>-<EDGE_ID>.

Workaround:

  1. Log into the Cloud Director Provider Portal as a System Administrator.
  2. Click on the affected Edge Gateway in Resources > Cloud Resources > Edge Gateways > Edge Name.
  3. Note the name on of the Edge as displayed in the Cloud Director UI under Configuration > General > Name.
    For example:

    Edge Name
    ExampleEdge
  4. Note the ID of the Edge as displayed in the URL of the browser after opening the Edge.
    For example:

    URL
    https:///provider/cloud/edge-gateways/cloud/urn:vcloud:gateway:1234abcd-####-####-####-############/config/general

    Edge ID
    1234abcd-####-####-####-############

  5. Using the Edge Name and Edge ID create the expected VRF Context name in the from <EDGE_NAME>-<EDGE_ID>.
    For example:

    VRF Context Name
    ExampleEdge-1234abcd-####-####-####-############

  6. Log into the Avi Load Balancer UI as an administrator.
  7. Open Infrastructure > Cloud Resources > VRF Context and under the Select Cloud dropdown select the Avi Cloud that is used with Cloud Director and the Edge Gateway in question.
  8. Search for the Edge ID of the affected Edge Gateway by clicking the search icon.
    For example:

    1234abcd-####-####-####-############

  9. Confirm that the Edge Name portion of the VRF Context name does NOT match the Edge Name in the Cloud Director UI.
  10. If the name is incorrect Edit the VRF Context and change the General > Name field to match the format expected by Cloud Director as constructed in step 5. above.
    For example:

    VRF Context Name
    ExampleEdge-1234abcd-####-####-####-############

  11. Save the name change and retry enabling Transparent Mode on the Edge Gateway in the Cloud Director UI.

Additional Information