starlingx
/
fault
Code Issues Proposed changes

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 <jagatguruprasad.mishra@windriver.com>
This commit is contained in:
Jagatguru Prasad Mishra 2023-11-23 06:23:08 -05:00
parent f8716aa344
commit 1684514c79
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
fm-doc/fm_doc/events.yaml
View File

@ -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=<hostname>
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