Error: Resource type: TIER1 is dependent on resource type: TIER0 during NSX Manager to Policy API migration in EAR

Products

• VMware Tanzu Platform Core
• VMware Tanzu Application Service
• VMware NSX

Issue/Introduction

When migrating from NSX Management Plane to Policy API for VMware Tanzu Application Service/EAR using the NCP tile, the Apply Changes task fails with exit code 1. This error occurs because the migration coordinator skips parent objects incorrectly tagged with the ncp/cluster scope. This article provides the steps to identify these tags and resolve the migration failure.

 

Symptoms:

• Check the migrate-mp2p VM created under the NCP deployment for logs located at /var/vcap/sys/log/migrate-mp2p/mp_to_policy_import.log, you will see errors like:
  
  [ERROR 2026-08-25T15:19:36Z]: Exception: The migration API returned with FAILURE status. Details:

          "error_id": "30542",
          "error_desc": "Resource type: <CHILD> is dependent on resource type: <PARENT> with id: #######-####-####-####-8b79f2626ca5. Please make sure that the dependent objects are promoted first or are not created by policy."
  
  
  • Examples:
    
    Failure for TIER0:
    "error_desc": "Resource type: TIER1 is dependent on resource type: TIER0 with id: #######-####-####-####-8b79f2626ca5. Please make sure that the dependent objects are promoted first or are not created by policy."
    
    Failure for IPBLOCK:
"error_desc": "Error while promoting IPBlockSubnet:########-####-####-####-105d41fb8fd7.Reason:MP Resource of type : IPBLOCK with id :########-####-####-####-0d6601d05ac1 not found on policy/not yet promoted."
    
    
• The logs show that mp2p script couldn't find the dependent NSX resource even though it was specified in the VMware NSX-T tile:
   
  [DEBUG 2026-08-24T19:44:14Z]: Filtering resources with user_spec file, exclusively including from user_spec for SharedResources.Tier0Router
  [WARNING 2026-08-24T19:44:14Z]: No resource found on MP with ID or display_name <NSX resource from tile> mentioned in the user spec file

Environment

VMware Tanzu Application Service/EAR

NSX 4.2.x

NCP 4.2.4

Cause

The NCP migration utility requires specific tagging to migrate objects. Manually applied tags with scope ncp/cluster on shared NSX resources (such as Tier-0 Logical Routers or IPBLOCKs) cause the migration coordinator to filter these objects out. Consequently, child objects fail to promote because their parent objects are excluded, resulting in dependency errors.

Resolution

To resolve this issue, identify and remove the problematic tags with scope: ncp/cluster from all manually created objects referenced in the NCP tile in the MP to Policy Migration section:

1. Remove the tag with scope: ncp/cluster from all NSX objects specified in the VMware NSX-t tile config pane in Opsmanager. This can be done via NSX GUI or API
2. Re-run the migrate-mp2p errand from Opsmanager

Additional Information

• If issues persist, please reach out to Broadcom Support. To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.
• For updates on fix status, reference: How to subscribe to Knowledge Base articles.