Description of problem (please be detailed as possible and provide log snippests): When I try to create a new PVPool via the OpenShift web console, the creation is rejected with the following error: >An error occurred >Error "Required value" for field "spec.pvPool.secret". Version of all relevant components (if applicable): ocs-operator.v4.5.0-448.ci 4.5.0-0.nightly-2020-06-10-201008 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes - I cannot create PVPools in this method Is there any workaround available to the best of your knowledge? It's possible to use the NooBaa management console or CLI tool to create PVPs. 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? Yes If this is a regression, please provide more details to justify this: Creation worked in OCS 4.4 Steps to Reproduce: 1. Go to Operators -> Installed Operators -> OCS -> Backing Store -> Create -> Provider=PVC 2. Fill out the necessary fields 3. Click on `Create Backing Store` Actual results: Error is shown Expected results: Creation is successful
Is this issue present in OCS 4.4 as well? It looks like this field has been made required in OCS4.5. What is the UI supposed to pass as a Secret in the case of PV Pools? If any secret is associated with a PV Pool Noobaa should be taking care of it. For other types of the backing store, it makes sense as these Secret's contain user credentials for the endpoint. It looks like this was introduced to fix issues where the secret is not being passed but in the case of PV Pool, it does not make sense for the UI to pass a secret. Nimrod what do you make of this?
Hey, The formula of a PVpool's Secret's Name is backing-store-pv-pool-{PVPoolName} when PVPoolName is the name of the PVpool. If I understood correctly it's also missing in the OLM so I'll add it.
Moving over to mcg
Verified, PV backing store created successfully as intended.
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 (Red Hat OpenShift Container Storage 4.5.0 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/RHBA-2020:3754