starlingx
/
fault
Code Issues Proposed changes

Add alarm id, definition for subcloud backup 

This commit adds a new alarm id and definition for subcloud backup.
The alarm will be raised and cleared by dcmanager upon subcloud backup
failure and successful retry respectively.

Test Plan:
 - Verify successful tox test and package build

Story: 2010116
Task: 46162
Change-Id: I9a34a827e484bb691c8ce0da63e1a7d26735c289
Signed-off-by: Tee Ngo <Tee.Ngo@windriver.com>
This commit is contained in:
Tee Ngo 2022-08-31 07:53:02 -04:00
parent e78a7eeb53
commit 80d6819635
2 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
fm-api/source/fm_api/constants.py
View File

@ -125,6 +125,7 @@ FM_LOG_ID_HYPERVISOR_STATE_CHANGE = ALARM_GROUP_HYPERVISOR + ".001"
# Distributed Cloud alarm id
FM_ALARM_ID_DC_SUBCLOUD_OFFLINE = ALARM_GROUP_DISTRIBUTED_CLOUD + ".001"
FM_ALARM_ID_DC_SUBCLOUD_RESOURCE_OUT_OF_SYNC = ALARM_GROUP_DISTRIBUTED_CLOUD + ".002"
FM_ALARM_ID_DC_SUBCLOUD_BACKUP_FAILED = ALARM_GROUP_DISTRIBUTED_CLOUD + ".003"
# HA alarm id
FM_ALARM_ID_HA_SERVICE_GROUP_STATE = ALARM_GROUP_HA + ".001"

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

@ -982,6 +982,20 @@
Management_Affecting_Severity: none
Degrade_Affecting_Severity: none
280.003:
Type: Alarm
Description: Subcloud Backup Failure
Entity_Instance_ID: subcloud=<subcloud>
Severity: minor
Proposed_Repair_Action: Retry subcloud backup after checking backup input file. If problem persists contact next level of support.
Maintenance_Action:
Inhibit_Alarms:
Alarm_Type: processing-error
Probable_Cause: unknown
Service_Affecting: False
Suppression: False
Management_Affecting_Severity: none
Degrade_Affecting_Severity: none
#---------------------------------------------------------------------------
# NETWORK