Bug 2172365

Summary:	[csi-addons] odf-csi-addons-operator oomkilled with fresh installation 4.12
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	James Biao <jbiao>
Component:	csi-addons	Assignee:	Rakshith <rar>
Status:	CLOSED ERRATA	QA Contact:	Joy John Pinto <jopinto>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.12	CC:	allee, jopinto, kbg, kramdoss, lema, mmuench, ndevos, ocs-bugs, odf-bz-bot, rar, tdesala
Target Milestone:	---
Target Release:	ODF 4.13.0
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, `odf-csi-addons-operator` had low memory resource limit and as a result the `odf-csi-addons-operator` pod was `OOMKill`ed (out of memory). With this fix, the default memory and the CPU resource limit has been increased and `odf-csi-addons-operator` `OOMKill`s are not observed.	Story Points:	---
Clone Of:
Clones:	2177184 (view as bug list)		Environment:
Last Closed:	2023-06-21 15:24:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2154341, 2177184

Description James Biao 2023-02-22 06:05:56 UTC

Description of problem (please be detailed as possible and provide log
snippests):

On Fresh installation ODF 4.12 pod csi-addons-controller-manager OOMKilled


Version of all relevant components (if applicable):
ODF 4.12

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
Always at customer's environment

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Install 4.12
2. observe odf-csi-addons-operator 
3.


Actual results:
odf-csi-addons-operator pod crashing

Expected results:
odf-csi-addons-operator running

Additional info:

Comment 22 Joy John Pinto 2023-06-19 05:57:34 UTC

Verified with OCP 4.13.0-0.nightly-2023-06-15-222927 and ODF 4.13.0

[jopinto@jopinto t]$ oc get po -l app.kubernetes.io/name=csi-addons -o yaml
apiVersion: v1
items:
.........
  spec:
    containers:
    - args:
      - --health-probe-bind-address=:8081
      - --metrics-bind-address=127.0.0.1:8080
      - --leader-elect
      - --enable-admission-webhooks=true
      command:
      - /manager
      env:
      - name: OPERATOR_CONDITION_NAME
        value: odf-csi-addons-operator.v4.13.0-rhodf
      image: quay.io/rhceph-dev/odf4-odf-csi-addons-rhel9-operator@sha256:7b9fc08c273584cf96a5c8a7310a3bfaf0125cda35cb5bf4087deaef1c66fb36
      imagePullPolicy: IfNotPresent
      livenessProbe:
        failureThreshold: 3
        httpGet:
          path: /healthz
          port: 8081
          scheme: HTTP
        initialDelaySeconds: 15
        periodSeconds: 20
        successThreshold: 1
        timeoutSeconds: 1
      name: manager
      ports:
      - containerPort: 9443
        name: webhook-server
        protocol: TCP
      readinessProbe:
        failureThreshold: 3
        httpGet:
          path: /readyz
          port: 8081
          scheme: HTTP
        initialDelaySeconds: 5
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 1
      resources:
        limits:
          cpu: "1"
          memory: 512Mi
        requests:
          cpu: 10m
          memory: 64Mi
      securityContext:
        allowPrivilegeEscalation: false
        capabilities:

Comment 24 errata-xmlrpc 2023-06-21 15:24:01 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix 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.

https://access.redhat.com/errata/RHBA-2023:3742