Policy import creates new parent policy or fails to nest under Default Policy in Aria Operations

Products

• VCF Operations

Issue/Introduction

• Importing a policy from one Aria Operations cluster to another creates a new parent policy (e.g., "Default Policy-1") instead of nesting as a child policy under the existing Default Policy.
  
  
• Imported policies are not applied to objects because they are not under the active Default Policy.

Environment

VMware Aria Operations 8.x

Cause

This issue occurs because Aria Operations uses unique UUIDs for policy hierarchies. When a policy is exported, the XML file contains a Parent policy key UUID. If this UUID does not exist or match the Default policy in the destination cluster, the system creates a new parent policy to maintain the hierarchy defined in the XML.

Resolution

To import a policy as a child of the existing Default Policy on a new site, align the XML metadata with the destination cluster's identifiers.

1. Navigate to Configurations > Policy Definition in the destination Aria Operations instance.
2. Select the Default Policy, click the ellipses, and select Export.
3. Open the exported XML file in a text editor and locate the Policy key field and copy the UUID.
4. Open the XML file of the policy to be imported.
5. Search for parentPolicy and replace the existing UUID with the one copied in Step 3.
6. Ensure the Parent policy name field matches the name of the destination parent (usually "Default Policy").
7. Save the modified XML file.
8. In the destination Aria Operations instance, delete the incorrectly created "Default Policy-1" hierarchy if a previous import was attempted.
9. Import the modified XML file.
10. The policy now appears as a child of the intended parent policy.