Bug 1912421 - [RFE] noobaa cli allow the creation of BackingStores with already existing secrets
Summary: [RFE] noobaa cli allow the creation of BackingStores with already existing se...
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: OCS 4.7.0
Assignee: Romy Ayalon
QA Contact: aberner
Depends On:
Blocks: 1874367 1938134
TreeView+ depends on / blocked
Reported: 2021-01-04 12:19 UTC by Martin Bukatovic
Modified: 2021-05-19 09:17 UTC (History)
8 users (show)

Fixed In Version: v4.7.0-249.ci
Doc Type: Enhancement
Doc Text:
.Use an existing secret to create a new backingstore With this enhancement, a new backing store can be created through the Multicloud Object Gateway CLI using an existing secret.
Clone Of:
Last Closed: 2021-05-19 09:17:18 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github noobaa noobaa-operator pull 526 0 None closed noobaa cli enhancement - Create backingstore and namespacestore by specifying existing secret name 2021-02-17 14:25:29 UTC
Github noobaa noobaa-operator pull 529 0 None closed Backport to 5.7 2021-02-17 14:25:30 UTC
Red Hat Product Errata RHSA-2021:2041 0 None None None 2021-05-19 09:17:45 UTC

Description Martin Bukatovic 2021-01-04 12:19:03 UTC
Description of problem

When one tries to create GCP backing store via noobaa cli, it doesn't allow
one to specify a secret created beforehand.

Based on previous discussing with Nimrod under bz 1873646, and later Bipul.

Version-Release number of selected component

OCP: 4.5.0-0.ci-2020-08-28-093348
OCS: 4.5.0-543.ci

How reproducible


Steps to Reproduce

1. Install OCP/OCS cluster
2. Install noobaa cli and configure it's access to OCS cluster
3. Try to create GCP backingstore using already existing k8s secret

Actual results

NooBaa CLI Command `backingstore create` for GCP doesn't provide a way to
specify already existing secret:


$ noobaa backingstore create google-cloud-storage -h
Create google-cloud-storage backing store

      --private-key-json-file='': private-key-json-file is the path to the json file provided by google for service
account authentication
      --target-bucket='': The target bucket name on Google cloud storage

  noobaa backingstore create google-cloud-storage <backing-store-name> [flags] [options]

Use "noobaa options" for a list of global command-line options (applies to all commands).

Expected results

It's possible to specify GCP credentials via k8s secret when creating GCP
backing store.

Comment 5 aberner 2021-02-04 10:37:42 UTC
OCP: 4.7.0-0.nightly-2021-02-03-225958
OCS: ocs-operator.v4.7.0-250.ci

Comment 11 errata-xmlrpc 2021-05-19 09:17:18 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.


Note You need to log in before you can comment on or make changes to this bug.