starlingx
/
fault
Code Issues Proposed changes

Change context for 400.001 and 400.002 alarms 

400.001 and 400.002 alarms are tagged for openstack but should be
starlingx.

This change tags them to starlingx so the documentation scripts are
able to classify them correctly.

Test plan
PASS: Check the parsing scripts end successfully.

Closes-bug: 2028379

Signed-off-by: Agustin Carranza <agustin.carranza@windriver.com>
Change-Id: I8f5966d5b0a7b82198e4bc2e735fa4536a4cdd0a
This commit is contained in:
Agustin Carranza 2023-07-21 11:09:50 -03:00
parent dbffaed98f
commit 5b94faf575
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1310,7 +1310,7 @@
Suppression: True
Management_Affecting_Severity: warning
Degrade_Affecting_Severity: major
Context: openstack
Context: starlingx
400.002:
@ -1334,7 +1334,7 @@
Suppression: True
Management_Affecting_Severity: warning
Degrade_Affecting_Severity: none
Context: openstack
Context: starlingx
400.003: