Description of problem
When one opens "Create new Backing Store" form and selects "Google cloud
storage" as a provider, it's no longer possible to select k8s secret with
credentials. User can only select a file with credentials to be loaded.
This behavior is unique for GCP platform. For all other cloud storage
providers available in this form:
- AWS S3
- S3 Compatible
- Azure blob
- IBM COS
The form shows "secret" form field, with an option to switch to credentials
I reported this bug based on OCS MCG dev's team evaluation of BZ 1873646:
Which suggests that user should have both options available (selecting either
already created secret or create new one).
Version-Release number of selected component
Steps to Reproduce
1. Install OCP/OCS cluster
2. Open OCP Console, and navigate to OCS operator
3. Go to "Backing Store" tab (where you will see list of backing stores,
such as noobaa-default-backing-store)
4. Click on "Create Backing Store" button
5. In "Create new Backing Store" page,
for provider select "Google cloud storage"
With "Google cloud storage" as selected provider, it's not possible to chose
k8s secret with authentication details for MCG to control the target bucket.
User can specify the credentials for the storage bucket via both:
- already existing k8s secret
- entering/loading new secret via "credentials" mode
as is the case for all other platforms available in this form.
Waiting on UXD, moving out of 4.6
This cannot be fixed until https://bugzilla.redhat.com/show_bug.cgi?id=1912421
Apparently, 1912421 is not required for this. Removing it as dependency. Moving it to assigned. And re-targeted for 4.7.
Using OCP 4.7.0-0.nightly-2021-02-04-132953 on GCP, I installed OCS 4.7.0-250.ci and was able to create new noobaa backing store via "Create Backing Store" page, reusing already existing k8s secret (created during installation for the default backing store). The new backing store then reached "Ready" state.
Created attachment 1755140 [details]
verification screenshot: Create new backing store page allows to select k8s secret with credentials now as expected
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: OpenShift Container Platform 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days