Browse Source

Adding alarm indicating k8s rootCA update start

Update in events.yaml adding alarm 900.008 indicating that procedure
for k8s root CA update started in the system.

Task: 2008675
Story: 42411
Signed-off-by: Joao Soubihe <JoaoPaulo.Soubihe@windriver.com>
Change-Id: I0df40423735e1c76acc21206b96c9e8b7924121f
changes/43/788943/4
Joao Soubihe 3 months ago
parent
commit
c50b3b8760
  1. 3
      fm-api/fm_api/constants.py
  2. 15
      fm-doc/fm_doc/events.yaml

3
fm-api/fm_api/constants.py

@ -294,6 +294,9 @@ FM_ALARM_ID_DEVICE_IMAGE_UPDATE_IN_PROGRESS = ALARM_GROUP_SW_MGMT + ".006"
# Kubernetes Upgrade alarm id
FM_ALARM_ID_KUBE_UPGRADE_IN_PROGRESS = ALARM_GROUP_SW_MGMT + ".007"
# Kubernetes RootCA Update alarm id
FM_ALARM_ID_KUBE_ROOTCA_UPDATE_IN_PROGRESS = ALARM_GROUP_SW_MGMT + ".008"
# Security log id
FM_LOG_ID_INVALID_PASSWORD = ALARM_GROUP_SECURITY + ".001"
FM_LOG_ID_USER_LOCKOUT = ALARM_GROUP_SECURITY + ".002"

15
fm-doc/fm_doc/events.yaml

@ -3124,6 +3124,21 @@
Management_Affecting_Severity: warning
Degrade_Affecting_Severity: none
900.008:
Type: Alarm
Description: Kubernetes rootca update in progress
Entity_Instance_ID: host=controller
Severity: minor
Proposed_Repair_Action: Wait for kubernetes rootca procedure to complete
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
900.101:
Type: Alarm
Description: Software patch auto-apply inprogress

Loading…
Cancel
Save