(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:

[Monitor:audit-log-analyzer][sig-arch][Late] operators should not create watch channels very often

Test has a 85.00% pass rate, but 95.00% is required.

Sample (being evaluated) Release: 4.21
Start Time: 2025-11-19T00:00:00Z
End Time: 2025-11-26T12:00:00Z
Success Rate: 85.00%
Successes: 17
Failures: 3
Flakes: 0
Base (historical) Release: 4.20
Start Time: 2025-09-21T00:00:00Z
End Time: 2025-10-21T23:59:59Z
Success Rate: 0.00%
Successes: 0
Failures: 0
Flakes: 0

View the test details report for additional context.

It is incredibly likely this is the result of a new change and the operator is creating slightly more watch requests. If the team can identify why the operator is suddenly using more, pinpoint the PR, then all that needs to happen here is to bump the allowed limits in origin. This seems to be showing on vsphere only so far. The current limit is 17 + some leeway, we're now seeing up to 40.

It would be good to identify why and confirm it's expected, but this is likely just maintenance of the test intended to prevent exponential watch growth.

Filed by: dgoodwin@redhat.com