The VMware Infrastructure Health MP alerts and symptoms definitions are missing from Aria Operations 8.18.x
Aria Operations 8.18.x
To resolve the issue, please follow the steps below.
Please note: The steps will clean up the orphaned SymptomRelationship rows.
/etc/init.d/vpostgres-repl start
su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433 -c \"COPY kv_symptomproblemdefinition TO '/tmp/kv_symptomproblemdefinition_$(date +%Y%m%d).csv' WITH (FORMAT CSV, HEADER TRUE);\""
zip /tmp/kv_symptomproblemdefinition_$(date +%Y%m%d).zip /tmp/kv_symptomproblemdefinition_$(date +%Y%m%d).csv
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-'))
);
\""
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-'))
);
\""
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-'))
);
\""
curl -ksS -w "%{http_code}" -X POST -u "admin" -H "Accept: application/json" "https://localhost/casa/upgrade/cluster/pak/VMwareInfrastructureHealth-818XXXX/operation/reinstall"
Please note: It will be required to find the minor version and the build number for the VMware Infrastructure version that is suitable for your environment. The information can be found in the path: /storage/db/pakRepoLocal/
Filename: VMwareInfrastructureHealth-818[minor version][build number]
- Make sure to pick the most recent/highest build number of the VMware Infrastructure Health MP.Check for the existence of expected Infrastructure Health MP alerts and symptoms in the Product UI