Description of problem: After deploying ACM and subsequently upgrading OCP on the hub cluster, the search-operator pod remains in OOMKilled/CrashLoopBackOff status. Version-Release number of selected component (if applicable): ACM 2.0.3 How reproducible: Varies. Steps to Reproduce: 1. Install ACM 2.0.3 2. Upgrade OpenShift on hub cluster Actual results: search-operator pod remains in OOMKilled/CrashLoopBackOff status. Expected results: search-operator pod remains in Running state. Additional info: When the search operator restarts, initial memory consumption spikes above 128Mi limit. After ~5 minutes it levels off to ~45Mi. Was able to work around the issue by changing the memory limit in the search-operator pod deployment to 256Mi. Graph from Grafana showing memory utilization above the 128Mi limit is attached. Also attaching output of oc describe pod.
Created attachment 1716631 [details] Graph of search-operator Pod Memory Utilization from Grafana
Created attachment 1716632 [details] oc describe for search-operator
I've increased the default memory limit to 256Mi as a quick fix to prevent this from happening. The change is merged for the next z-release 2.0.4 and for 2.1 I'll keep this issue open to investigate why the memory consumption has increased and track a permanent code fix.
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 for Kubernetes version 2.0.4 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/RHSA-2020:4304