-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.21
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Approved
-
None
-
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:
[OCPFeatureGate:InsightsOnDemandDataGather] test_datagather_marked_as_failed[trigger_on_demand_collection0]
Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 60.00%.
Sample (being evaluated) Release: 4.21
Start Time: 2025-12-30T00:00:00Z
End Time: 2026-01-06T16:00:00Z
Success Rate: 60.00%
Successes: 9
Failures: 6
Flakes: 0
Base (historical) Release: 4.20
Start Time: 2025-09-21T00:00:00Z
End Time: 2025-10-21T23:59:59Z
Success Rate: 100.00%
Successes: 23
Failures: 0
Flakes: 0
View the test details report for additional context.
Also hits a half dozen other tests which will show up shortly when this is triaged to the regressions.
We need something addressed or an SBAR as techpreview needs to be kept functional on the release blocking board.
Why did these tests start running on Dec 27th after the pencils down date? I would not expect new tests to appear in this window. Are these insights operator tests supposed to be blocking signal in component readiness or are they just being picked up incidentally, in which case they need to be reclassified as excluded/hidden in https://github.com/openshift/sippy/blob/master/pkg/variantregistry/ocp.go
Filed by: dgoodwin@redhat.com