Bug 2032984 - After creating a new SC it redirects to 404 error page instead of the "StorageSystems" page
Summary: After creating a new SC it redirects to 404 error page instead of the "Storag...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ODF 4.10.0
Assignee: gowtham
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On: 2033251 2033366
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-15 16:21 UTC by Itzhak
Modified: 2023-12-08 04:27 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-13 18:50:40 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-operator pull 160 0 None open console: update compatibility support matrix for 4.10 2021-12-21 15:15:32 UTC
Red Hat Product Errata RHSA-2022:1372 0 None None None 2022-04-13 18:51:13 UTC

Description Itzhak 2021-12-15 16:21:42 UTC
Description of problem (please be detailed as possible and provide log
snippets):
After creating the SC in AWS OCP 4.10, ODF 4.9 it leads to a 404 error page instead of the "StorageSystems" page(URL: "/odf/cluster/systems"). The SC was created successfully.


Version of all relevant components (if applicable):
OCP 4.10, ODF 4.9.

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No, it still works. But it is not the expected behaviour.

Is there any workaround available to the best of your knowledge?
No.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes.

Can this issue reproduce from the UI?
Yes


If this is a regression, please provide more details to justify this:
Yes, in the previous versions we didn't get this kind of error.

Steps to Reproduce:
1. Deploy an AWS 4.10 cluster, without ODF.
2. Install ODF 4.9 through the UI.
3. Create a new StorageSystem. 


Actual results:
After creating and installing the StorageSystem it redirects to a 404 page.


Expected results:
After creating and installing the StorageSystem it should redirect to the "StorageSystems" page. 

Additional info:

Comment 2 gowtham 2021-12-16 11:41:22 UTC
Please make sure the option  "Console Plugin" is enabled,
   Go to OperatorHub => Installed Operators => OpenShift Data Foundation
   Check option  "Console plugin" is showing status "Enabled"
   If not then change to "Enable"  by clicking the hyperlink

Comment 5 Bipul Adhikari 2021-12-16 11:51:12 UTC
Currently due to changes in the SDK, ODF 4.9 + OCP 4.10 is breaking. We have a bug to track the fix for that https://bugzilla.redhat.com/show_bug.cgi?id=2033251

Comment 6 Mugdha Soni 2021-12-21 10:23:38 UTC
Hi

The same issue was encountered with following builds as well :-

[root@localhost dnd-odf]# 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

[root@localhost dnd-odf]# oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2021-12-14-083101   True        False         21h     Cluster version is 4.10.0-0.nightly-2021-12-14-083101


Thanks 
Mugdha

Comment 7 gowtham 2021-12-21 12:04:38 UTC
I can also reproduce this with ODF 4.10 + OCP 4.10. Will send a fix.

Thanks 
Gowtham S

Comment 11 Mugdha Soni 2022-01-11 15:22:50 UTC
Hi 

Tested the fix with following versions

Comment 12 Mugdha Soni 2022-01-12 08:04:36 UTC
Hi Gowtham 

Tested with the following builds :- 
OCP : 4.10.0-0.nightly-2022-01-11-065245
ODF : 4.10.0-79

It was observed that after the creation of storage system , when clicked on refresh console popup it was redirected to operator hub wizard under operator dashboard.
Whereas it should redirect you to storage--> openshift data foundation-->storage system .

Plus it would be a great help if u could mention in which version is this fixed .



Thanks
Mugdha Soni

Comment 13 Mudit Agarwal 2022-01-12 08:09:25 UTC
Normally we put the Fixed in version, but in this case the BZ was fixed long back so you can just test with the latest stable build.

Comment 14 Mugdha Soni 2022-01-12 08:11:36 UTC
(In reply to Mugdha Soni from comment #12)
> Hi Gowtham 
> 
> Tested with the following builds :- 
> OCP : 4.10.0-0.nightly-2022-01-11-065245
> ODF : 4.10.0-79
> 
> It was observed that after the creation of storage system , when clicked on
> refresh console popup it was redirected to operator hub wizard under
> operator dashboard.
> Whereas it should redirect you to storage--> openshift data
> foundation-->storage system .
> 
> Plus it would be a great help if u could mention in which version is this
> fixed .
> 
> 
> 
> Thanks
> Mugdha Soni

Please ignore the above mentioned information . Apologies
After creating storage system , no 404 error was encountered and console was redirected to  "StorageSystems" page . 

Hence moving this bug to verified . 

Thanks 
Mugdha Soni

Comment 19 errata-xmlrpc 2022-04-13 18:50:40 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.10.0 enhancement, security & bug fix 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:1372

Comment 20 Red Hat Bugzilla 2023-12-08 04:27:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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