Bug 2013930

Summary: Create Buttons enabled for Bucket Class, Backingstore and Namespace Store in the absence of Storagesystem(or MCG)
Product: OpenShift Container Platform Reporter: Neha Berry <nberry>
Component: Console Storage PluginAssignee: Pranshu Srivastava <prasriva>
Status: CLOSED ERRATA QA Contact: Mugdha Soni <musoni>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.9CC: afrahman, aos-bugs, ebenahar, nthomas, prasriva
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:19:35 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:
Attachments:
Description Flags
screencast of the issue none

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:
Overview 
Storagesystem
"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:
====================
Always


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)
5. 


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:
==================
https://chat.google.com/room/AAAA76Pbvwc/0XTY6qFCf0E
Comment 5 Mugdha Soni 2021-11-12 08:53:39 UTC 
Blocked due to https://bugzilla.redhat.com/show_bug.cgi?id=2022631.

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

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 .

Thanks 
Mugdha
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.

https://access.redhat.com/errata/RHSA-2022:0056