Description of problem (please be detailed as possible and provide log snippests): csi-addons-controller-manager pod is going into CLBO state. Version of all relevant components (if applicable): 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? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? yes Can this issue reproduce from the UI? - If this is a regression, please provide more details to justify this: yes, indexer fix was added in 4.17 Steps to Reproduce: You can get a storageclassName to nil by - create a PVC with a sc - edit PV to set persistentVolumeReclaimPolicy: Retain - backup PVC and remove SCName, .status and everything other than name/namespace in .metadata - backup PV and remove SCName, .spec.Claimref , .status and everything other than name/namespace in .metadata - delete pvc & pv from cluster - apply the backed up pv yaml and then pvc yaml Delete the csi-addons pod, watch it go into CLBO state. Actual results: csi-addons pod goes into CLBO state. Expected results: csi-addons pod should run normally. Additional info: refer to - https://github.ibm.com/ProjectAbell/abell-tracking/issues/41847 - https://github.com/csi-addons/kubernetes-csi-addons/pull/685 -
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.17.0 Security, Enhancement, & 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-2024:8676