-
Bug
-
Resolution: Unresolved
-
Normal
-
4.17.0, 4.18.0, 4.19.0, 4.20.0, 4.21.0, 4.22.0
-
Quality / Stability / Reliability
-
False
-
-
3
-
Moderate
-
No
-
None
-
None
-
MCO Sprint 283, MCO Sprint 284
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
mcd_config_drift metric is not cleared properly.
Description:
When a config drift happens mcd_config_drift metric is updated, but if we delete the MCD pod running on the node where the config drift happened the metric is cleared.
Reproduce
1. Force a config drift in a node
The mcd_config_drift metric will report the drift properly
2. Remove the MCD pod that is running in the node where the drift happened
Current behaviour:
The metric is set to "0" after the MCD pod is removed.
Expected behaviour:
The metric should only be set to "0" when the config drift stops happening.
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- is related to
-
MCO-1954 Investigate what improvements can be made to the config drift monitor
-
- To Do
-
- relates to
-
MCO-1 Observability Infrastructure and Enhanced metrics in MCO
-
- Closed
-
-
MCO-681 Add Key State Metrics
-
- Closed
-
-
MCO-899 Pre-merge Testing
-
- Closed
-
- links to
