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 csi-addons which currently runs client-go version v0.26.2 on release-4.13. Since OCP-4.14 has +1/-1 support matrix with ODF, similar issue can be hit on csi-addons 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:
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 (Important: Red Hat OpenShift Data Foundation 4.13.3 security 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/RHSA-2023:5376