Stale dc-cert alarm for an already unmanaged and deleted subcloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Kyle MacLeod |
Bug Description
Brief Description
-----------------
After a subcloud was unmanaged and deleted, a dc-cert out-of-sync alarm (280.002) continued to be reported. The expected behavior is not see any alarms related to deleted subclouds as this creates a confusion for an operator
Severity
--------
Minor
Steps to Reproduce
------------------
- dcmanager subcloud unmanage
- dcmanager subcloud delete
- Check alarms
Expected Behavior
------------------
Alarms related to the deleted subcloud are removed
Actual Behavior
----------------
A dc-cert out-of-sync alarm is still present
Reproducibility
---------------
Intermittent
System Configuration
-------
Distributed Cloud
Branch/Pull Time/Commit
-------
stx.5.0; not sure if issue also exists in stx master
Last Pass
---------
Unknown
Timestamp/Logs
--------------
cert-mon.log.* shows the following errors related to the subcloud even after a deletion:
2021-10-
2021-10-
2021-10-
2021-10-
2021-10-
2021-10-
2021-10-
2021-10-02 00:03:03.292 187857 ERROR sysinv.
2021-10-
Test Activity
-------------
Testing
Workaround
----------
Manually delete the alarm
Changed in starlingx: | |
assignee: | nobody → Kyle MacLeod (kmacleod) |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: stx.distcloud |
description: | updated |
description: | updated |
tags: | added: stx.7.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /distcloud/ +/820534
Review: https:/