-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.19.0
-
Quality / Stability / Reliability
-
False
-
-
3
-
3
-
Important
-
None
-
None
-
Rejected
-
Metal Platform 274, Metal Platform 275, Metal Platform 276
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:
[bz-Bare Metal Hardware Provisioning] clusteroperator/baremetal should not change condition/Degraded
Test has a 81.25% pass rate, but 95.00% is required.
Sample (being evaluated) Release: 4.19
Start Time: 2025-06-05T00:00:00Z
End Time: 2025-06-12T08:00:00Z
Success Rate: 81.25%
Successes: 13
Failures: 3
Flakes: 0
Base (historical) Release: 4.18
Start Time: 2025-01-26T00:00:00Z
End Time: 2025-02-25T23:59:59Z
Success Rate: 0.00%
Successes: 0
Failures: 0
Flakes: 0
View the test details report for additional context.
This seems to be a relatively new problem, first hit Jun 7, three total times since then. The operator is going degraded when it shouldn't. I reports a message like:
source/OperatorDegraded display/true condition/Degraded reason/ResourceNotFound status/True metal3 deployment inaccessible [36s]