Bug 2081908 - Performance issue to get secret in claim-controller
Summary: Performance issue to get secret in claim-controller
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.4.z
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: rhacm-2.4.5
Assignee: daliu
QA Contact: Hui Chen
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-05 00:44 UTC by daliu
Modified: 2022-06-27 17:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-27 17:04:02 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.4.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 22237 0 None None None 2022-05-05 02:23:04 UTC
Red Hat Product Errata RHSA-2022:5201 0 None None None 2022-06-27 17:04:16 UTC

Description daliu 2022-05-05 00:44:56 UTC
Description of the problem:
In collective env, the claim controller can not work with error:

E0317 18:54:58.707698       1 reflector.go:138] sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:224: Failed to watch *v1.Secret: failed to list *v1.Secret: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 95845; INTERNAL_ERROR
I0317 18:56:22.806925       1 trace.go:205] Trace[1641125135]: "Reflector ListAndWatch" name:sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:224 (17-Mar-2022 18:55:11.391) (total time: 71415ms):
Trace[1641125135]: [1m11.415663055s] [1m11.41…

details please see: https://github.com/stolostron/backlog/issues/21301

Comment 1 daliu 2022-05-13 02:26:41 UTC
@huichen please help to verify it. Thank you

Comment 2 Hui Chen 2022-06-07 13:08:34 UTC
 Verified with v2.4.5-FC0

Comment 8 errata-xmlrpc 2022-06-27 17:04:02 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 (Moderate: Red Hat Advanced Cluster Management 2.4.5 security updates and bug fixes), 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:5201


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