Network resources show as “Missing” in deployments after NSX-T cloud account re-creation in VCF Automation

Products

• VCF Automation

Issue/Introduction

In VCF Automation, deployments shows network resources in a “Missing” state after NSX-T cloud account re-creation.

• Deployment initially succeeds
• Network resource appears as Missing in topology

catalog-service-app pod logs shows the below error:

WARN catalog-service-app [host='catalog-service-app-8686c69bf8-sw7kj' thread='boundedElastic-446' trace='69b79b10acf0c5af5387a444354ad4aa'] c.v.t.d.service.ResourceSyncServiceImpl - Resource with id: of type: 'Cloud.vSphere.Network' and origin: 'DEPLOYED', reported missing with error: 410 Gone from POST https://tango-blueprint.prelude.svc.cluster.local:8080/blueprint/api/blueprint-deployments/fetch-resource-state 

Environment

VCF Automation 9.x 

Cause

The NSX-T cloud account was deleted and re-created.

This results in:

• New endpoint IDs being generated
• Existing deployments still referencing old endpoint links
• Resource sync failures → network marked as Missing

 

Resolution

Do NOT delete the NSX-T cloud accounts if active deployments exist.

• Validate dependencies before deletion
• Contact Broadcom Support before making such changes