"Internal server error" when modifying policies in Aria Operations due to Duplicate Symptom Definitions

Products

• VCF Operations

Issue/Introduction

• When attempting to edit and save a Policy in the Aria Operations UI, the operation fails and displays the error: "Internal server error"

• Reviewing the /storage/log/vcops/log/web.log file on the Primary node shows logging indicating a duplicate key:

  ERROR [aaa-bbb-#.#.#.#-port-exec-####] com.vmware.vcops.bridge.client.DataRetrieverClient.execute - com.vmware.vcops.platform.gemfire.GemfireFunction$MethodInvocationException: IllegalStateException: Duplicate key SymptomDefinition-vCloud-VcloudDatastoreRunningOutOfStorageSpaceWarning (attempted merging values com.vmware.vcops.platform.api.model.policy.pkg.pagination.SymptomItem@####### and com.vmware.vcops.platform.api.model.policy.pkg.pagination.SymptomItem@########)

• Manually deleting the duplicate symptom definition from the UI only temporarily resolves the issue, as the system immediately fails on the next duplicated symptom in the database.

Environment

Aria Operations 8.18.6

Resolution

Restarting the Aria Operations nodes flushes the corrupted memory cache, clearing the ghost duplicate keys and allowing you to save policies.

1. Log in to the Aria Operations Administrator interface (https://<Primary-Node-IP>/admin).
2. Under Cluster Status, click Take Offline to gracefully shut down the cluster.
3. Once the cluster is fully offline, click Bring Online.
4. Log back into the standard UI and verify that policies can now be saved.

Permanent Fix: Reset Management Pack Default Content

To permanently resolve the backend database duplication, you must perform a repair installation of the affected Management Pack to overwrite and rebuild the OOTB content cleanly.

1. Download the appropriate Management Pack .pak file (e.g., VMware Cloud Director Management Pack) from the Broadcom Support Portal that matches your Aria Operations version.
2. In Aria Operations, navigate to Data Sources > Integrations > Repository.
3. Click Add/Upgrade on the affected Management Pack tile.
4. Browse and select the .pak file.
5. Install the PAK file even if it is already installed
6. Reset Default Content (This command forces the database to drop all corrupted default symptoms and rewrite a single, clean list).
7. Complete the installation.