Bug 2013930 - Create Buttons enabled for Bucket Class, Backingstore and Namespace Store in the absence of Storagesystem(or MCG)
Summary: Create Buttons enabled for Bucket Class, Backingstore and Namespace Store in ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Pranshu Srivastava
QA Contact: Mugdha Soni
Depends On:
TreeView+ depends on / blocked
Reported: 2021-10-14 07:18 UTC by Neha Berry
Modified: 2022-03-10 16:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:19:35 UTC
Target Upstream Version:

Attachments (Terms of Use)
screencast of the issue (766.39 KB, video/webm)
2021-10-14 07:18 UTC, Neha Berry
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10324 0 None open Bug 2013930: Disable ODF BackingStore, BucketClass, and NamespaceStore tabs and OCS BlockPool tab. 2021-10-26 13:42:40 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:19:54 UTC

Description Neha Berry 2021-10-14 07:18:11 UTC
Created attachment 1832829 [details]
screencast of the issue

Description of problem:
Currently with latest OCP versions and OCS 4.9, the Storage->Openshift Data Foundation menu gets enabled post ODF Operator install from OperatorHub.

The following tabs appaear even when Storagesystem is not yet created and the following are listed:
"Backing Store"
"Bucket Class" and 
"namespace Storage" 

In the absence of any Storagesystem, we still get the buttons highlighted for Backing Store , Bucket Class and Namespace Store. What if customers try to create them  ?  Until we have Noobaa configured(MCG-only or full deployment), shouldn't we keep these buttons disabled or these tabs hidden?

Version-Release number of selected component (if applicable):
OCP - 4.9.0-0.nightly-2021-10-12-084355
OCS = ocs-operator.v4.9.0

noobaa-operator.v4.9.0   NooBaa Operator               4.9.0                Succeeded
ocs-operator.v4.9.0      OpenShift Container Storage   4.9.0                Succeeded
odf-operator.v4.9.0      OpenShift Data Foundation     4.9.0                Succeeded

How reproducible:

Steps to Reproduce:
1. Install OCP 4.9
2. Create catalogsource for 4.9 ODF
3. Install ODF operator from Operator Hub
4. Check the Storage->Openshift Data Foundation appears post installation of the operator(Do not create storagesystem)

Actual results:
Check the users get option to Create  "Backing Store" "Bucket Class" and "namespace Storage" even when MCG is not enabled/installed

Expected results:
Either the tabs should not appear until MCG is deployed(Storagesystem is created) or the Create Button should be disabled

Additional info:

Comment 5 Mugdha Soni 2021-11-12 08:53:39 UTC
Blocked due to https://bugzilla.redhat.com/show_bug.cgi?id=2022631.


Comment 7 Mugdha Soni 2021-11-15 09:27:17 UTC

Validated the fix with following versions :-

OCP :4.10.0-0.nightly-2021-11-14-184249
ODF : 4.9.0-237.ci

**UPI AWS cluster was created for validation of fix.

**Observations :-

The following tabs were missing after successful ODF operator installation(no storage system created) :-

(i) Backing Store
(ii)Bucket Class  
(iii)Namespace Storage

** [root@localhost test_1]# oc get storagecluster
No resources found in openshift-storage namespace.

**Screenshot for the same is attached in comment #6

Based on comment#6 and comment#7 moving the bug to verified state .


Comment 10 errata-xmlrpc 2022-03-10 16:19:35 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: OpenShift Container Platform 4.10.3 security 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.