Hide Forgot
OpenShift engineering has decided to NOT ship 4.8.6 on 8/23 due to the following issue. https://bugzilla.redhat.com/show_bug.cgi?id=1995785 All the fixes part will be now included in 4.8.7 on 8/30.
G2Bsync 912079337 comment CrystalChun Thu, 02 Sep 2021 21:43:18 UTC G2Bsync Dupe issue https://github.com/open-cluster-management/backlog/issues/14619 Changes should go into 2.3.2 https://github.com/open-cluster-management/backlog/issues/15524 Awaiting verification from AI team that this issue is correct.
G2Bsync 925890290 comment CrystalChun Thu, 23 Sep 2021 14:52:48 UTC G2Bsync Will be included in 2.3.3 https://github.com/open-cluster-management/backlog/issues/16469
Hey sure, 1. Deploy assisted service 2. check CPU/Memeory 3. create 1K secrets that are not related to assisted-service, cluster deployment etc. 4. check CPU/Memeory again, it should not increase
Verified on: Hub cluster OCP version: 4.8.0 RHACM downstream snapshot: 2.3.3-DOWNSTREAM-2021-10-12-15-26-20 CPU/memory used by assisted-service did not increase after creating 1000 secrets in different namespace. Output before generating 1000 secrets: # kubectl top pods -n rhacm NAME CPU(cores) MEMORY(bytes) assisted-service-fc9d58d94-q6z7x 4m 204Mi Output after generating 1000 secrets: assisted-service-fc9d58d94-q6z7x 4m 204Mi
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: Red Hat Advanced Cluster Management 2.3.3 bug fix, security, and image updates), 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-2021:3925