Bug 2035175 - ODF dashboard not present under storage tab in UI.
Summary: ODF dashboard not present under storage tab in UI.
Keywords:
Status: CLOSED DUPLICATE of bug 2033251
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.10
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Bipul Adhikari
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-23 07:38 UTC by Mugdha Soni
Modified: 2023-08-09 16:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-05 06:22:20 UTC
Embargoed:

Attachments (Terms of Use)

Description Mugdha Soni 2021-12-23 07:38:26 UTC 
Description of problem :-
----------------------------
The Openshift data foundation wizard is absent under storage dashboard.

Version of all relevant components :
-------------------------------------
OCP :- 4.10.0-0.nightly-2021-12-18-034942

[root@localhost test]# oc get csv -n openshift-storage
NAME                   DISPLAY                       VERSION   REPLACES   PHASE
mcg-operator.v4.10.0   NooBaa Operator               4.10.0                           Succeeded
ocs-operator.v4.10.0   OpenShift Container Storage   4.10.0               Succeeded
odf-operator.v4.10.0   OpenShift Data Foundation     4.10.0               Succeeded


Can this issue reproducible?
------------------------------
YES

Can this issue reproduce from the UI?
--------------------------------------
Yes

Steps to Reproduce:
---------------------
1.Deploy OCP 4.10 and indtall ODF operator.
2. Create storage system and then click on storage tab .

Actual results:
--------------------
The ODF dashboard is missing.

Expected results:
-------------------
The ODF dashboard should be present under storage tab .
Comment 4 Bipul Adhikari 2022-01-05 06:22:20 UTC 

*** This bug has been marked as a duplicate of bug 2033251 ***
Note You need to log in before you can comment on or make changes to this bug.