From ad5e224dd2bf986437a1f7f09eabed9456e43938 Mon Sep 17 00:00:00 2001
From: Agustin Carranza <agustin.carranza@windriver.com>
Date: Thu, 1 Jun 2023 16:38:54 -0300
Subject: [PATCH] Remove 800.103 and modify documentation reference

Some alarms reference to "System Administration Manual" but this
document does not exist. It was changed to a generic documentation
reference.

The 800.103 alarm has been deprecated so it is deleted from the
events.yaml file.

Test plan
Pass:
* Build fm-doc package. Check that all parsing checks were run and
package was built successfully.

Closes-bug: 2022104

Signed-off-by: Agustin Carranza <agustin.carranza@windriver.com>
Change-Id: I4723d05e77983796a0f64c7242f5c2bcf4699763
---
 fm-doc/fm_doc/events.yaml | 27 ++-------------------------
 1 file changed, 2 insertions(+), 25 deletions(-)

diff --git a/fm-doc/fm_doc/events.yaml b/fm-doc/fm_doc/events.yaml
index a35ffd34..842b959e 100755
--- a/fm-doc/fm_doc/events.yaml
+++ b/fm-doc/fm_doc/events.yaml
@@ -199,7 +199,7 @@
     Entity_Instance_ID: fs_name=<image-conversion>
     Severity: critical
     Proposed_Repair_Action: "Add image-conversion filesystem on both controllers.
-                             Consult the System Administration Manual for more details.
+                             Consult the documentation for more details.
                              If problem persists, contact next level of support."
     Maintenance_Action: degrade
     Inhibit_Alarms:
@@ -3315,29 +3315,6 @@
     Degrade_Affecting_Severity: none
     Context: openstack
 
-800.103:
-    Type: Alarm
-    Description: |-
-        Storage Alarm Condition:
-        [ Metadata usage for LVM thin pool <VG name>/<Pool name> exceeded threshold and automatic extension failed,
-          Metadata usage for LVM thin pool <VG name>/<Pool name> exceeded threshold ]; threshold x%, actual y%.
-    Entity_Instance_ID: <hostname>.lvmthinpool=<VG name>/<Pool name>
-    Severity: critical
-    Proposed_Repair_Action: "Increase Storage Space Allotment for Cinder on the 'lvm' backend.
-                             Try the following commands:
-                             'vgextend <VG name> <PV name>' or 'vgextend -L +<size extension> <PV name>
-                             Check status with 'vgdisplay'
-                             Consult the System Administration Manual for more details.
-                             If problem persists, contact next level of support."
-    Maintenance_Action:
-    Inhibit_Alarms:
-    Alarm_Type: operational-violation
-    Probable_Cause: threshold-crossed
-    Service_Affecting: False
-    Suppression: False
-    Management_Affecting_Severity: major
-    Degrade_Affecting_Severity: none
-    Context: starlingx
 
 800.104:
     Type: Alarm
@@ -3351,7 +3328,7 @@
                              'system storage-backend-delete <storage-backend-name>'
                              AND
                              'system storage-backend-add <storage-backend-name>'
-                             Consult the System Administration Manual for more details.
+                             Consult the documentation for more details.
                              If problem persists, contact next level of support."
     Maintenance_Action:
     Inhibit_Alarms: