Description of problem: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-capi-operator/60/pull-ci-openshift-cluster-capi-operator-main-e2e-azure-capi-techpreview/1534099096451682304 Run #0: Failed expand_less 5s { fail [github.com/openshift/origin/test/extended/apiserver/api_requests.go:449]: Expected <[]string | len:1, cap:1>: [ "Operator \"cluster-capi-operator\" produces more watch requests than expected: watchrequestcount=77, upperbound=72, ratio=1.0694444444444444", ] to be empty} Version-Release number of selected component (if applicable): 4.11 Additional info:
Mike, could you please detail how to check the number of watches and what you have found for this particular operator, it would be nice to see why we need to increase the limit
Looks like passing now - "ctrl+f" "[sig-arch][Late] operators should not create watch channels very often [Suite:openshift/conformance/parallel]" https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-capi-operator/67/pull-ci-openshift-cluster-capi-operator-main-e2e-azure-techpreview/1547925464150970368/artifacts/e2e-azure-techpreview/openshift-e2e-test/artifacts/e2e.log Additional Info : Moved to VERIFIED. Please add any more info , in case needed to document .
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069