Bug 2094342 - apirequests limits of Cluster CAPI Operator are too low for Azure platform
Summary: apirequests limits of Cluster CAPI Operator are too low for Azure platform
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Mike Fedosin
QA Contact: Milind Yadav
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-07 12:44 UTC by Mike Fedosin
Modified: 2022-08-10 11:16 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:16:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin pull 27225 0 None open Bug 2094342: bump cluster-capi-operator apirequests upper bound to 50 2022-06-07 12:50:52 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:16:59 UTC

Description Mike Fedosin 2022-06-07 12:44:54 UTC
Description of problem:

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:

Comment 1 Joel Speed 2022-06-16 13:18:48 UTC
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

Comment 4 Milind Yadav 2022-07-19 14:10:33 UTC
Looks like passing now - "ctrl+f"  "[sig-arch][Late] operators should not create watch channels very often [Suite:openshift/conformance/parallel]" 


Additional Info :
Moved to VERIFIED.
Please add any more info , in case needed to document .

Comment 5 errata-xmlrpc 2022-08-10 11:16:50 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.