Description of problem (please be detailed as possible and provide log snippests): Upload a file using encryption to a noobaa bucket results with Internal error 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)? 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: Steps to Reproduce: 1. run a put-object with encryption enabled 2. for example: aws-cli aws s3api put-object --no-verify-ssl --endpoint-url <noobaa-endpoint> --bucket <bucket> --key <new-key> --body <object_to_upload> --server-side-encryption AES256 Actual results: Internal Error Expected results: { "ETag": "\"9e7e6f7fb78bd7dc0d38f2e8cd316d8f\"", "ServerSideEncryption": "AES256" } Additional info:
Verified on: OCP: 4.6.0-0.nightly-2020-11-07-035509 OCS: 4.6.0-156.ci
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.6.0 security, bug fix, 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-2020:5605