Add Kubernetes RootCA Update orch alarms and events

Kubernetes rootca update alarms are 900.5xx series

The new alarms are similar in numbering and wording as the
kube upgrade auto apply 900.4xx series alarms and logs.

Story: 2008675
Task: 42708
Signed-off-by: albailey <Al.Bailey@windriver.com>
Change-Id: I480dc50b1cb03d12cc7ba2a7eefad80d3c56e32c
This commit is contained in:
albailey 2021-06-25 16:39:55 -05:00
parent c50b3b8760
commit 544bb3f74a
2 changed files with 161 additions and 0 deletions

View File

@ -373,6 +373,23 @@ FM_LOG_ID_KUBE_UPGRADE_AUTO_APPLY_ABORT_REJECTED = ALARM_GROUP_SW_MGMT + ".419"
FM_LOG_ID_KUBE_UPGRADE_AUTO_APPLY_ABORT_FAILED = ALARM_GROUP_SW_MGMT + ".420"
FM_LOG_ID_KUBE_UPGRADE_AUTO_APPLY_ABORTED = ALARM_GROUP_SW_MGMT + ".421"
FM_ALARM_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_INPROGRESS = ALARM_GROUP_SW_MGMT + ".501"
FM_ALARM_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_ABORTING = ALARM_GROUP_SW_MGMT + ".502"
FM_ALARM_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_FAILED = ALARM_GROUP_SW_MGMT + ".503"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_START = ALARM_GROUP_SW_MGMT + ".511"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_INPROGRESS = ALARM_GROUP_SW_MGMT + ".512"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_REJECTED = ALARM_GROUP_SW_MGMT + ".513"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_CANCELLED = ALARM_GROUP_SW_MGMT + ".514"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_FAILED = ALARM_GROUP_SW_MGMT + ".515"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_COMPLETED = ALARM_GROUP_SW_MGMT + ".516"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_ABORT = ALARM_GROUP_SW_MGMT + ".517"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_ABORTING = ALARM_GROUP_SW_MGMT + ".518"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_ABORT_REJECTED = ALARM_GROUP_SW_MGMT + ".519"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_ABORT_FAILED = ALARM_GROUP_SW_MGMT + ".520"
FM_LOG_ID_KUBE_ROOTCA_UPDATE_AUTO_APPLY_ABORTED = ALARM_GROUP_SW_MGMT + ".521"
FM_ALARM_STATE_SET = 'set'
FM_ALARM_STATE_CLEAR = 'clear'
FM_ALARM_STATE_MSG = 'msg'

View File

@ -3714,4 +3714,148 @@
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.501:
Type: Alarm
Description: Kubernetes rootca update auto-apply inprogress
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: major
Proposed_Repair_Action: Wait for kubernetes rootca update auto-apply to complete; if problem persists contact next level of support
Maintenance_Action:
Inhibit_Alarms:
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: True
Suppression: True
Management_Affecting_Severity: warning
Degrade_Affecting_Severity: none
900.502:
Type: Alarm
Description: Kubernetes rootca update auto-apply aborting
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: major
Proposed_Repair_Action: Wait for kubernetes rootca update auto-apply abort to complete; if problem persists contact next level of support
Maintenance_Action:
Inhibit_Alarms:
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: True
Suppression: True
Management_Affecting_Severity: warning
Degrade_Affecting_Severity: none
900.503:
Type: Alarm
Description: Kubernetes rootca update auto-apply failed
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Proposed_Repair_Action: Attempt to apply kubernetes rootca update manually; if problem persists contact next level of support
Maintenance_Action:
Inhibit_Alarms:
Alarm_Type: equipment
Probable_Cause: underlying-resource-unavailable
Service_Affecting: True
Suppression: True
Management_Affecting_Severity: warning
Degrade_Affecting_Severity: none
900.511:
Type: Log
Description: Kubernetes rootca update auto-apply start
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.512:
Type: Log
Description: Kubernetes rootca update auto-apply inprogress
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.513:
Type: Log
Description: Kubernetes rootca update auto-apply rejected
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.514:
Type: Log
Description: Kubernetes rootca update auto-apply cancelled
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.515:
Type: Log
Description: Kubernetes rootca update auto-apply failed
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.516:
Type: Log
Description: Kubernetes rootca update auto-apply completed
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.517:
Type: Log
Description: Kubernetes rootca update auto-apply abort
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.518:
Type: Log
Description: Kubernetes rootca update auto-apply aborting
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.519:
Type: Log
Description: Kubernetes rootca update auto-apply abort rejected
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.520:
Type: Log
Description: Kubernetes rootca update auto-apply abort failed
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
900.521:
Type: Log
Description: Kubernetes rootca update auto-apply aborted
Entity_Instance_ID: orchestration=kube-rootca-update
Severity: critical
Alarm_Type: equipment
Probable_Cause: unspecified-reason
Service_Affecting: False
...