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:
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:
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