Bug 1934000

Summary: Improve error logging for kv-v2 while using encryption with KMS
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Rachael <rgeorge>
Component: rookAssignee: Sébastien Han <shan>
Status: CLOSED ERRATA QA Contact: Rachael <rgeorge>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.7CC: jthottan, madam, muagarwa, nberry, ocs-bugs, shan
Target Milestone: ---   
Target Release: OCS 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.7.0-283.ci Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-19 09:20:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rachael 2021-03-02 09:21:29 UTC 
Description of problem (please be detailed as possible and provide log
snippets):

When KV secret engine version 2 (kv-v2) is used while deploying encryption with KMS, the deployment fails, since the API calls differ between v1 and v2 and OCS uses v1 as the default, for these calls. Proper error/warning logs 
to indicate the same are missing .

Version of all relevant components (if applicable):
OCS: ocs-operator.v4.7.0-278.ci
OCP: 4.7.0-0.nightly-2021-03-01-085007

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
It is difficult to debug why the deployment failed

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 a backend path in the vault server with kv-v2
   # vault secrets enable -path=ocs kv-v2
2. Use the above created path to deploy OCS with encryption enabled using KMS


Actual results:
Deployment fails without proper error/warning logs

Expected results:
The logs should have proper warning message for the cause of failure.
Comment 7 errata-xmlrpc 2021-05-19 09:20:01 UTC 
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