Description of problem (please be detailed as possible and provide log snippests): For HPCS KMS, UI creates a Secret (containing IBM_KP_SERVICE_API_KEY & IBM_KP_CUSTOMER_ROOT_KEY) in openshift-storage namespace. Name of that Secret needs to be passed in: cephCluster.Spec.Security.KeyManagementService.TokenSecretName nooBaa.Spec.Security.KeyManagementService.TokenSecretName 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? 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: When UI creates a ocs-kms-connection-details configMap for IBM HPCS KMS all that information is passed down to Noobaa/Rook CR, but currently the name of the Secret is not getting passed to "Spec.Security.KeyManagementService.TokenSecretName" of these two CRs. Expected results: Secret name read from the configMap should be passed to "Spec.Security.KeyManagementService.TokenSecretName" of the CR. Additional info:
Acking this based on discussion with Mudit "It is a part of dev preview HPCS feature which IBM is testing, so our side regression only. Also, this is just a bug fix for IBM"
Moving to VERIFIED based on regression testing done post ODF 4.10.0-132
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.10.0 enhancement, security & 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-2022:1372