Alarm "Configuration is out-of-date" is not cleared after service http/https port change
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Andy |
Bug Description
Brief Description
-----------------
Alarm "Configuration is out-of-date" is not cleared after modify,apply service http to a new port
Severity
--------
Minor
Steps to Reproduce
------------------
1)Modify the service http to new port 8887 with the followig command
system service-
2)Apply the new config with the following command
system service-
[sysadmin@
+------
| uuid | service | section | name | value | personality | resource |
+------
| ca737769-
| | | | ort | | | |
| | | | | | | |
| 601b6a05-
| | | | port | | | |
| | | | | | | |
3)verify the alarms
[sysadmin@
+------
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+------
| 250.001 | controller-0 Configuration is out-of-date. | host= | major | 2020-01-10T |
| | | controller-0 | | 18:24:05. |
| | | | | 489544 |
| | | | | |
Expected Behavior
------------------
The alarm "Configuration is out-of-date" should be cleared after config applied on all the hosts
Actual Behavior
----------------
The alarm "Configuration is out-of-date" is not cleared and stays forever
Reproducibility
---------------
100%
System Configuration
-------
tested on all the following systems
one node system,http,ipv4
standard system,http,ipv4
one node system,http,ipv6
Branch/Pull Time/Commit
-------
2020-01-09
Last Pass
---------
may,2019
Timestamp/Logs
--------------
2020-01-
Test Activity
-------------
Feature Automation
Workaround
----------
Delete the alarm manually by "fm alarm-delete <uuid>"
description: | updated |
description: | updated |
tags: | added: stx.retestneeded |
Changed in starlingx: | |
status: | New → Triaged |
stx.4.0 / medium priority - stale alarm / workaround is to clear it manually