In VMware Aria Automation, deleting a deployment either due to lease expiry or manual removal may fail to clean up NSX-T components, such as Tier-1 Gateways, Segments, and NAT rules.
Even when the "Ignore Delete Failures" option is used, the deployment is removed from the Aria Automation UI but the underlying NSX resources remain, leading to issues like IP conflicts or deployment failures in future provisioning attempts.
This issue occurs when virtual machines or dependent resources are manually deleted before the deployment is fully removed.
The deletion task (ComputeNatRemovalTaskService) fails due to missing references, with errors such as:
Task failed with: Router state with URI http://##.##.##.##:8282/resources/routers/#######-####-####-####-########## is not found"Manual validation in NSX confirms that the Tier-1 Gateway, Segment, and NAT entries still exist after the deployment is force-deleted.
Please avoid manually deleting deployment resources, to prevent this issue and allow lease expiry or delete actions to handle the complete deployment cleanup.
Else we need to perform Manual Cleanup if the dependent objects (like VMs or interfaces) are deleted manually.
Manual Workaround Steps:
Delete NAT entries associated with the Tier-1 Gateway.
Delete the Segment attached to the gateway.
Delete the Tier-1 Gateway in NSX.
Perform force deletion in Aria Automation using the "Ignore Delete Failures" option.
Manual cleanup ensures NSX components are fully removed, avoiding conflicts in future deployments.
Additional errors reference missing network interfaces marked as deleted.
Caused by java.lang.IllegalStateException: Service marked deleted: /resources/network-interfaces/#######-####-####-####-##########at com.vmware.xenon.common.Operation.failServiceMarkedDeleted(Operation.java:288)
Manual checks in NSX confirm Tier-1, Segment, and NAT entries still exist post-deletion.