-
Bug
-
Resolution: Done
-
Normal
-
4.13.0
-
No
-
Hypershift Sprint 234, Hypershift Sprint 235, Hypershift Sprint 236
-
3
-
False
-
Description of problem:
The hypershift_hostedclusters_failure_conditions metric produced by the HyperShift operator does not report a value of 0 for conditions that no longer apply. The result is that if a hostedcluster had a failure condition at a given point, but that condition has gone away, the metric still reports a count for that condition.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Create a HostedCluster, watch the hypershift_hostedclusters_failure_conditions metric as failure conditions occur. 2. 3.
Actual results:
A cluster count of 1 with a failure condition is reported even if the failure condition no longer applies.
Expected results:
Once failure conditions no longer apply, 0 clusters with those conditions should be reported.
Additional info:
The metric should report an accurate count for each possible failure condition of all clusters at any given time.
- blocks
-
OCPBUGS-13085 hypershift_hostedclusters_failure_conditions metric incorrectly reports multiple clusters for a single cluster
- Closed
- is cloned by
-
OCPBUGS-13085 hypershift_hostedclusters_failure_conditions metric incorrectly reports multiple clusters for a single cluster
- Closed
- links to
- mentioned on