Bug 2082538 - apirequests limits of Cluster CAPI Operator are too low for GCP platform
Summary: apirequests limits of Cluster CAPI Operator are too low for GCP 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: sunzhaohua
Depends On:
TreeView+ depends on / blocked
Reported: 2022-05-06 11:34 UTC by Mike Fedosin
Modified: 2022-08-10 11:11 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:10:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin pull 27108 0 None open Bug 2082538: bump cluster-capi-operator apirequests upper bound for GCP 2022-05-06 11:43:52 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:11:11 UTC

Description Mike Fedosin 2022-05-06 11:34:08 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=63, upperbound=38, ratio=1.6578947368421053",
to be empty}

Version-Release number of selected component (if applicable): 4.11

Additional info:
GCP Cluster API provider

Comment 1 Mike Fedosin 2022-05-06 11:36:00 UTC
This bug blocks our CI, and we can't merge anything. So I'm setting its severity to high.

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