Created attachment 1710919 [details] multicluster-operators-standalone-subscription OOM log file Description of problem: in RHACM and CP4MCM integration env, the multicluster-operators-standalone-subscription pod restarting regularly due to OOMkilled for memory usage. increasing the memory limit to 2Gi solved the problem, monitoring shows its memory usage is around 650Mi, original memory limit is 512Mi. Version-Release number of selected component (if applicable): Build: 2.0.0-SNAPSHOT-2020-07-22-20-24-07 How reproducible: Steps to Reproduce: 1.install RHACM 2.0 2.install CP4MCM Actual results: Expected results: Additional info:
Root Cause: not enough memory allocated to the standalone subscription container. The memory limit of the multicluster-operators-standalone-subscription pod has been increased to 2G in the multicluster subscription community operator CSV. But this resource limit setting is ignored by OLM. This happens when OLM deploys all operators, not only the multicluster subscription operator. This will be documented in ACM 2.2
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 (Red Hat Advanced Cluster Management for Kubernetes version 2.2 images), 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/RHEA-2021:0729