Bug 2233028

Summary: Avoid pods entering into CrashLoopBackOff due to older k8s.io/client-go packages
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Karthik U S <ksubrahm>
Component: csi-driverAssignee: Karthik U S <ksubrahm>
Status: VERIFIED --- QA Contact: Sidhant Agrawal <sagrawal>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.13CC: kramdoss, ndevos, odf-bz-bot, sagrawal
Target Milestone: ---Flags: kramdoss: needinfo+
Target Release: ODF 4.13.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.13.3-2 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Karthik U S 2023-08-21 07:47:36 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
OCP-4.14 has a dependency on the k8s.io/client-go library which should be on version v0.26.4 or higher to avoid pods entering into the CrashLoopBackOff state when aggregated discovery is enabled on kube 1.27+ environments, as seen in the bz #2228319.

This bz is to handle the same for ceph-csi which currently runs client-go version v0.26.1 on release-4.13. Since OCP-4.14 has +1/-1 support matrix with ODF, similar issue can be hit on csi with release-4.13.


Version of all relevant components (if applicable):
OCP-4.14.0
ODF-4.13.1


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?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:
Comment 3 Karthik U S 2023-08-21 07:50:04 UTC 
Upstream PR: https://github.com/ceph/ceph-csi/pull/4053
Comment 4 Karthik U S 2023-08-21 09:59:13 UTC 
Backport: https://github.com/red-hat-storage/ceph-csi/pull/180