starlingx
/
fault
Code Issues Proposed changes

Merge "Remove 250.002 alarm from events.yaml file"

This commit is contained in:
Zuul 2023-06-20 20:17:23 +00:00 committed by Gerrit Code Review
parent de22b91ed5 063021cd70
commit dbffaed98f
2 changed files with 0 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -80,8 +80,6 @@ FM_ALARM_ID_SYSCONFIG_OUT_OF_DATE = ALARM_GROUP_SYSCONFIG + ".001"
# Deprecation followed the removal of the compute-config-complete command.
# FM_ALARM_ID_CONFIG_REQD = ALARM_GROUP_SYSCONFIG + ".010"
FM_ALARM_ID_CEPH_CACHE_TIER_CONFIG_OUT_OF_DATE = ALARM_GROUP_SYSCONFIG + ".002"
# Backup/Restore Alarm id
FM_ALARM_ID_BACKUP_IN_PROGRESS = ALARM_GROUP_BACKUP_RESTORE + ".001"
FM_ALARM_ID_RESTORE_IN_PROGRESS = ALARM_GROUP_BACKUP_RESTORE + ".002"

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

@ -932,21 +932,6 @@
Degrade_Affecting_Severity: none
Context: starlingx
250.002:
Type: Alarm
Description: <hostname> Ceph cache tiering configuration is out-of-date.
Entity_Instance_ID: cluster=<dist-fs-uuid>
Severity: major
Proposed_Repair_Action: Apply Ceph service parameter settings.
Maintenance_Action:
Inhibit_Alarms:
Alarm_Type: operational-violation
Probable_Cause: unspecified-reason
Service_Affecting: False
Suppression: False
Management_Affecting_Severity: warning
Degrade_Affecting_Severity: none
Context: starlingx
250.003:
Type: Alarm