Alarm Hostname controller function has in-service failure reported
When compute services remain healthy:
- listing alarms shall not refer to the below Obsoleted alarm
- 200.012 alarm hostname controller function has an in-service failure
This update deletes definition of the obsoleted alarm and any references
200.012 is removed in events.yaml file
Also updated any reference to this alarm definition.
Need to also raise a Bug to track the Doc change.
Test Plan:
Verify on a Standard configuration no alarms are listed for
hostname controller in-service failure
Code (removal) changes exercised with fix prior to ansible bootstrap
and host-unlock and verify no unexpected alarms
Regression:
There is no need to test the alarm referred here as they are obsolete
Reviewed: https:/ /review. opendev. org/c/starlingx /metal/ +/860095 /opendev. org/starlingx/ metal/commit/ 86681b75985a457 112db57b4d59469 be3fb8a73e
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 86681b75985a457 112db57b4d59469 be3fb8a73e
Author: Girish Subramanya <email address hidden>
Date: Mon Oct 3 10:04:55 2022 -0400
Alarm Hostname controller function has in-service failure reported
When compute services remain healthy:
- listing alarms shall not refer to the below Obsoleted alarm
- 200.012 alarm hostname controller function has an in-service failure
This update deletes definition of the obsoleted alarm and any references
200.012 is removed in events.yaml file
Also updated any reference to this alarm definition.
Need to also raise a Bug to track the Doc change.
Test Plan:
Verify on a Standard configuration no alarms are listed for
hostname controller in-service failure
Code (removal) changes exercised with fix prior to ansible bootstrap
and host-unlock and verify no unexpected alarms
Regression:
There is no need to test the alarm referred here as they are obsolete
Closes-Bug: 1991531
Signed-off-by: Girish Subramanya <email address hidden>
Change-Id: I255af68155c539 2ea42244b931516 f742fa838c3