Description of problem: CI tests for 4.10 are flaking with the cluster-monitoring operator reporting too many watches: [sig-arch][Late] operators should not create watch channels very often [Suite:openshift/conformance/parallel] "Operator \"cluster-monitoring-operator\" produces more watch requests than expected: watchrequestcount=69, upperbound=66, ratio=1.0454545454545454" Version-Release number of selected component (if applicable): 4.10 How reproducible: Sometimes Steps to Reproduce: Mainly non-IPI tests seem to be impacted (example - 4.10 aws-upgrade) Actual results: [sig-arch][Late] operators should not create watch channels very often [Suite:openshift/conformance/parallel] test fails Expected results: Tests pass Additional info: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/22451/rehearse-22451-pull-ci-openshift-builder-release-4.10-openshift-e2e-aws-builds-techpreview/1452970495040294912
The fix for https://bugzilla.redhat.com/show_bug.cgi?id=2016352 might improve this.
IIUC this is a generic issue with this e2e test checking that operators don't create too many watches and nothing specific to the cluster monitoring operator. The following PRs should improve the situation: https://github.com/openshift/origin/pull/26583 https://github.com/openshift/origin/pull/26601