Bug 2274676

Summary: CSI Pods going into OOM during volume group restore
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Madhu Rajanna <mrajanna>
Component: ocs-client-operatorAssignee: Leela Venkaiah Gangavarapu <lgangava>
Status: CLOSED ERRATA QA Contact: Jilju Joy <jijoy>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.15CC: asriram, kramdoss, lgangava, muagarwa, nberry, odf-bz-bot, omitrani
Target Milestone: ---   
Target Release: ODF 4.15.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: isf-provider
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 2274675 Environment:
Last Closed: 2024-06-11 16:41:15 UTC Type: ---
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: 2274675    
Bug Blocks:    

Description Madhu Rajanna 2024-04-12 07:07:55 UTC
+++ This bug was initially created as a clone of Bug #2274675 +++

In internal mode CSI Pods doesn't have any resource limits set probably due to the proportional requirement wrt increase in PV requirement and provider mode also should remove the limits set to match internal mode.

Tracker for https://github.ibm.com/ProjectAbell/abell-tracking/issues/34944

--- Additional comment from RHEL Program Management on 2024-04-12 06:53:31 UTC ---

This bug having no release flag set previously, is now set with release flag 'odf‑4.16.0' to '?', and so is being proposed to be fixed at the ODF 4.16.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.

--- Additional comment from RHEL Program Management on 2024-04-12 06:53:31 UTC ---

The 'Target Release' is not to be set manually at the Red Hat OpenShift Data Foundation product.

The 'Target Release' will be auto set appropriately, after the 3 Acks (pm,devel,qa) are set to "+" for a specific release flag and that release flag gets auto set to "+".

Comment 8 Jilju Joy 2024-05-17 10:17:16 UTC
Verified in version:

% oc get csv
NAME                                    DISPLAY                            VERSION        REPLACES                                PHASE
ocs-client-operator.v4.15.3-rhodf       OpenShift Data Foundation Client   4.15.3-rhodf   ocs-client-operator.v4.14.6-rhodf       Succeeded
odf-csi-addons-operator.v4.15.3-rhodf   CSI Addons                         4.15.3-rhodf   odf-csi-addons-operator.v4.14.6-rhodf   Succeeded

% oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.15.11   True        False         2d2h    Cluster version is 4.15.11

Based on the discussions, the verification step is to verify that the resources limit and request is removed

% oc get deployment csi-rbdplugin-provisioner -oyaml | yq '.spec .template .spec .containers[] | [.name, .resources]';
- csi-provisioner
- {}
- csi-attacher
- {}
- csi-resizer
- {}
- csi-snapshotter
- {}
- csi-rbdplugin
- {}

 
% oc get deployment csi-cephfsplugin-provisioner -oyaml | yq '.spec .template .spec .containers[] | [.name, .resources]';
- csi-provisioner
- {}
- csi-attacher
- {}
- csi-resizer
- {}
- csi-snapshotter
- {}
- csi-cephfsplugin
- {} 


% oc get daemonset csi-cephfsplugin -oyaml | yq '.spec .template .spec .containers[] | [.name, .resources]'
- csi-driver-registrar
- {}
- csi-cephfsplugin
- {}


% oc get daemonset csi-rbdplugin -oyaml | yq '.spec .template .spec .containers[] | [.name, .resources]'
- csi-driver-registrar
- {}
- csi-rbdplugin
- {}
- csi-addons
- {}

Comment 13 errata-xmlrpc 2024-06-11 16:41:15 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.15.3 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-2024:3806