From 1684514c7955dd74852c001064e77964afc18da8 Mon Sep 17 00:00:00 2001 From: Jagatguru Prasad Mishra Date: Thu, 23 Nov 2023 06:23:08 -0500 Subject: [PATCH] Add LUKS alarm in fm doc Maintenance service raises an alarm with ID 200.016 if luks-fs-mgr service is inactive. This change adds the description of 200.016 alarm. Test Plan: PASS: build-pkgs -c -p fm-doc PASS: build-image PASS: AIO-SX bootstrap with LUKS service status inactive. A critical alarm with ID 200.016 should be displayed while listing the alarm using 'fm alarm-list' Story: 2010872 Task: 49125 Depends-On: https://review.opendev.org/c/starlingx/metal/+/901455 Change-Id: Iadee64bffbb37cfd94aa735f7eeb12ba0fa86fbd Signed-off-by: Jagatguru Prasad Mishra --- fm-doc/fm_doc/events.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/fm-doc/fm_doc/events.yaml b/fm-doc/fm_doc/events.yaml index e57630b5..47e39cde 100755 --- a/fm-doc/fm_doc/events.yaml +++ b/fm-doc/fm_doc/events.yaml @@ -787,6 +787,21 @@ Degrade_Affecting_Severity: none Context: starlingx +200.016: + Type: Alarm + Description: Issue in creation or unsealing of LUKS volume + Entity_Instance_ID: host= + Severity: critical + Proposed_Repair_Action: If auto-recovery is consistently unable to recover host to the unlocked-enabled state contact next level of support or lock and replace failing host. + Maintenance_Action: None + Inhibit_Alarms: False + Alarm_Type: operational-violation + Probable_Cause: unknown + Service_Affecting: False + Suppression: False + Management_Affecting_Severity: major + Degrade_Affecting_Severity: none + Context: starlingx 200.020: Type: Log