This issue affects Aria Operations 8.10.x or later. There is no resolution at this time.
Workaround:
It is recommended to take snapshots following How to take a Snapshot of VMware Aria Operations before following the workaround steps.
To work around this issue, remove orphaned symptom relationships from the database.
- Log into the Primary node as root via SSH or Console.
- Run the following command to export the current symptom and alert definitions table to a csv file:
su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433 -c \"COPY kv_symptomproblemdefinition TO '/tmp/kv_symptomproblemdefinition.csv' WITH (FORMAT CSV, HEADER TRUE);\""
- Copy the /tmp/kv_symptomproblemdefinition.csv file to a location other than the primary node as a backup.
- Run the following command to get a list of orphaned SymptomRelationship rows in the kv_symptomproblemdefinition table:
su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433 -c \"
SELECT sr.key
FROM kv_symptomproblemdefinition AS sr
WHERE sr.key LIKE 'SymptomRelationship-SymptomDefinition-%'
AND NOT EXISTS (
SELECT *
FROM kv_symptomproblemdefinition AS sd
WHERE sd.key = RIGHT(sr.key, -LENGTH('SymptomRelationship-'))
);\""
Note: If no rows are returned, contact support for additional troubleshooting.
- Run the following command to delete the orphaned SymptomRelationship rows:
su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433 -c \"
DELETE FROM kv_symptomproblemdefinition AS sr
WHERE sr.key LIKE 'SymptomRelationship-SymptomDefinition-%'
AND NOT EXISTS (
SELECT *
FROM kv_symptomproblemdefinition AS sd
WHERE sd.key = RIGHT(sr.key, -LENGTH('SymptomRelationship-'))
);\""
- Optional: Retry the upgrade or management pack install.
- Verify expected symptom and alert definitions now exist in the Aria Operations UI.