Route map deletion process is stuck in the NSX-T UI.
search cancel

Route map deletion process is stuck in the NSX-T UI.


Article ID: 322562


Updated On:


VMware NSX Networking


  • Deleting a route map for a T0 gateway does not seem to work: the route map deletion process is stuck in the UI.
  • NSX-T logs shows the realization error below:
INFO providerTaskExecutor-7 PolicyProviderUtil - POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="policy"] Created alarm Alarm [policyPath=/infra/realized-state/enforcement-points/default/tier-0-logical-routers/gw01/route-maps/Deny_T0/alarms/973fff87-021b-4912-a0c5-41b51bf84f2d, message=Realization failure, waiting for realization of [{PrefixList}]: path=[/infra/tier-0s/gw01/prefix-lists/fc3dac7c-7767-42dc-9baa-bd9b6306f6aa], Realization will be reattempted in next cycle (max 5 minutes),errorId=PROVIDER_INVOCATION_FAILURE, path=null, apiError=null, sourceSiteId=null].
INFO policyProviderTaskScheduler-2 ConsolidatedRealizedStateServiceImpl - POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="policy"] Updated consolidated state for intentPath:/infra/tier-0s/gw01/route-maps/Deny_T0 to:ERROR
INFO providerTaskExecutor-36 RealizationFetchUtility - POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="policy"] Added dependent paths:[/infra/tier-0s/gw01/route-maps/Deny_T0] on:/infra/tier-0s/gw01/prefix-lists/fc3dac7c-7767-42dc-9baa-bd9b6306f6aa
  • The route map shows as marked for delete in the following API call:
GET policy/api/v1/infra/tier-0s/gw01/route-maps/?include_mark_for_delete_objects=true
            "resource_type": "Tier0RouteMap",
            "id": "Deny_T0",
            "display_name": "Deny T0",
            "path": "/infra/tier-0s/gw01/route-maps/Deny_T0",
            "relative_path": "Deny_T0",
            "parent_path": "/infra/tier-0s/gw01",
            "unique_id": "6e05f413-4a59-4a50-b936-c65d1475065b",
            "marked_for_delete": true,


VMware NSX-T Data Center 3.x
VMware NSX-T Data Center


If a route-map does not get realized, possibly because of a configuration error, such as an invalid IP prefix list, this results in the realized resource ID set to "null".

When the route map is subsequently deleted from the UI, the deletion process will check for the realized resource ID and since it is "null" it will skip it.


The issue is resolved in NSX-T version 3.1.3 available at VMware Downloads.

Additional Information

There is no real impact however the deleted object is still seen in the UI and in the related API response.