Alarm 250.001 raised after Sub-cloud install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Girish Subramanya |
Bug Description
After system controller and subcloud install success, one DX subcloud (subcloud-3) got 250.001 alarm.
250.001 | controller-1 Configuration is out-of-date. (applied: 4965d3f5-
Severity
--------
Minor
Steps to Reproduce
------------------
install DC subcloud
Expected Behavior
------------------
No Alarms expected after successful sub-cloud install
Actual Behaiour
After installation, there is 250.001 alarm
Reproducibility
---------------
The issue is observed on 1 sub-cloud of 10 sub-clouds installed.
Additional Information
-------
The Alarm that persisted was for Config UUID with the reload-required, which was not cleared after first install
Software version
----------------
Releases 22.06 Patch_0007
Changed in command-not-found: | |
assignee: | nobody → Girish Subramanya (gisubram) |
affects: | command-not-found → starlingx |
Changed in starlingx: | |
status: | New → In Progress |
tags: | added: stx.distcloud stx.fault |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.8.0 |
Reviewed: https:/ /review. opendev. org/c/starlingx /config/ +/869535 /opendev. org/starlingx/ config/ commit/ a5cf7d2b45c71d3 5483d356d9a552f 7b580cebda
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit a5cf7d2b45c71d3 5483d356d9a552f 7b580cebda
Author: Girish Subramanya <email address hidden>
Date: Sun Jan 8 20:50:00 2023 -0500
Alarm 250.001 persists after first install on sub-cloud
After system controller and subcloud install success, one DX subcloud
witnessed a 250.001 alarm; the alarm was seen on one of 10 sub-clouds
The Alarm that persisted is for Config UUID with reload-required set
The Alarm was seen on the Standby Subcloud controller on a DX subcloud
Performing comparison of configured manifest post restart with target
The clear of the reboot_required config_target is based on the First
Report from sysinv-agent occuring within a limited time after restart
Test Plan:
Verify SX Subcloud Install is successful and no 250.001 alarm exists
Verify DX Subcloud Install is successful and no 250.001 alarm exists
Verify for reboot required config eg. ‘system ntp-modify’,
Alarm persists till next lock/unlock sequence
Regression:
Verify AIO-SX, AIO-DX Install is successful
Verify Distributed Clod Controller and Sub-cloud install is successful
Verify for reboot required config eg. ‘system ntp-modify’,
Alarm persists till next lock/unlock sequence
Closes-Bug: 2002258
Signed-off-by: Girish Subramanya <email address hidden> 3925cd009f6be8b b1c140a210f
Change-Id: I95f0642c97367a