Bug 2084041 - [Console Migration] Link-able storage system name directs to blank page
Summary: [Console Migration] Link-able storage system name directs to blank page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.11.0
Assignee: Vineet
QA Contact: Mugdha Soni
URL:
Whiteboard:
: 2086431 2087669 (view as bug list)
Depends On:
Blocks: 2086431
TreeView+ depends on / blocked
 
Reported: 2022-05-11 09:12 UTC by Mugdha Soni
Modified: 2023-08-09 16:46 UTC (History)
12 users (show)

Fixed In Version: 4.11.0-96
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-24 13:52:56 UTC
Embargoed:


Attachments (Terms of Use)
Blank page (54.14 KB, image/png)
2022-05-11 09:12 UTC, Mugdha Soni
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/red-hat-storage odf-console pull 208 0 None None None 2022-06-08 08:10:28 UTC
Github https://github.com/red-hat-storage odf-console pull 209 0 None None None 2022-06-08 08:10:28 UTC
Red Hat Product Errata RHSA-2022:6156 0 None None None 2022-08-24 13:53:23 UTC

Description Mugdha Soni 2022-05-11 09:12:34 UTC
Created attachment 1878602 [details]
Blank page

Description of problem :-
-----------------------------

After successful creation of storage system , when directed to storage --> data foundation --> storage systems and click on link-able system name .. it takes to a blank page and is stuck there . 


Version of all relevant components :
-------------------------------------
OCP :- 4.11
ODF :- 4.11.0-67


Does this issue impact your ability to continue to work with the product
-------------------------------------------------------------------------
yes

Is there any workaround available to the best of your knowledge?
----------------------------------------------------------------- 
no



Can this issue reproducible?
-------------------------------
Yes


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


Steps to Reproduce:
---------------------

1.Install ODF 4.11 operator
2. Create storage system .
3. Direct to storage --> data foundation --> storage systems.


Actual results:
--------------------
Blank page is present instead of block and file and object service dashboard. 


Expected results:
--------------------
Block and file and object service dashboard is present .

Comment 4 Mudit Agarwal 2022-05-17 06:26:35 UTC
Bipul, please attach the PR link to this BZ

Comment 5 Mudit Agarwal 2022-05-17 12:06:13 UTC
*** Bug 2086431 has been marked as a duplicate of this bug. ***

Comment 9 gowtham 2022-05-25 13:57:14 UTC
*** Bug 2087669 has been marked as a duplicate of this bug. ***

Comment 11 Mugdha Soni 2022-06-20 14:46:39 UTC
Validated the fix using cluster with following versions :

OCP :

[root@localhost ui]# oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-06-15-222801   True        False         4h4m    Cluster version is 4.11.0-0.nightly-2022-06-15-222801


ODF :

[root@localhost ui]# oc get csv odf-operator.v4.11.0 -o yaml -n openshift-storage| grep full_version
    full_version: 4.11.0-96
          f:full_version: {}


The link able storage system name directs to Block and file and object dashboard (Screenshot for the same is attached in comment#9 ) .

Hence moving the bug to verified state.


Thanks
Mugdha Soni

Comment 14 errata-xmlrpc 2022-08-24 13:52:56 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 (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix 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:6156


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