From 4ab96ad4114735366fc7841377465ea70e6e50b7 Mon Sep 17 00:00:00 2001 From: Andy Ning Date: Fri, 23 Jul 2021 22:00:48 -0400 Subject: [PATCH] Update event.yaml for alarm 250.003 This change updated 250.003 definition in events.yaml so it's consistent with the alarm actually raised in kube-cert-rotation.sh. Depends-On: https://review.opendev.org/c/starlingx/config/+/802610 Closes-Bug: 1937288 Signed-off-by: Andy Ning Change-Id: I13404483c22ded4d35c613576f1d2020b31c1797 --- fm-doc/fm_doc/events.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fm-doc/fm_doc/events.yaml b/fm-doc/fm_doc/events.yaml index ba3996f4..a3184884 100755 --- a/fm-doc/fm_doc/events.yaml +++ b/fm-doc/fm_doc/events.yaml @@ -832,10 +832,10 @@ 250.003: Type: Alarm - Description: Kubernetes certificates rotation failed on host . + Description: "Kubernetes certificates rotation failed on host[, reason = ]" Entity_Instance_ID: host= Severity: major - Proposed_Repair_Action: Rotate kubernetes certificates manually. + Proposed_Repair_Action: Lock and unlock the host to update services with new certificates (Manually renew kubernetes certificates first if renewal failed). Maintenance_Action: Inhibit_Alarms: Alarm_Type: operational-violation