Description of problem (please be detailed as possible and provide log snippets): PVC creation using RBD storageclass where encryption is enabled using KMS fails with the following error: I0203 10:17:38.463042 1 connection.go:183] GRPC request: {"capacity_range":{"required_bytes":2147483648},"name":"pvc-29170a51-9575-420b-af4e-d0a176ca6779","parameters":{"clusterID":"openshift-storage","encrypted":"true","encryptionKMSID":"1-vault","imageFeatures":"layering","imageFormat":"2","pool":"ocs-storagecluster-cephblockpool"},"secrets":"***stripped***","volume_capabilities":[{"AccessType":{"Mount":{"fs_type":"ext4"}},"access_mode":{"mode":1}}]} I0203 10:17:38.475791 1 connection.go:185] GRPC response: {} I0203 10:17:38.475821 1 connection.go:186] GRPC error: rpc error: code = InvalidArgument desc = invalid encryption kms configuration: failed to parse kms configuration: unexpected end of JSON input I0203 10:17:38.475839 1 controller.go:752] CreateVolume failed, supports topology = false, node selected false => may reschedule = false => state = Finished: rpc error: code = InvalidArgument desc = invalid encryption kms configuration: failed to parse kms configuration: unexpected end of JSON input Version of all relevant components (if applicable): OCP: 4.7.0-0.nightly-2021-02-02-223803 OCS: ocs-operator.v4.7.0-250.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Provisioning for encrypted RBD PVC fails Is there any workaround available to the best of your knowledge? Not that I am aware of Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: No Steps to Reproduce: 1. Create an RBD storageclass with encryption enabled 2. Create a secret containing the token from vault 3. Create an RBD PVC using the storageclass in step 1 Actual results: PVC is stuck in Pending state with the following error: I0203 10:17:38.475839 1 controller.go:752] CreateVolume failed, supports topology = false, node selected false => may reschedule = false => state = Finished: rpc error: code = InvalidArgument desc = invalid encryption kms configuration: failed to parse kms configuration: unexpected end of JSON input Expected results: PVC creation should be successful
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 (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement 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-2021:2041