Bug 2082888 - IBM StorageSystem redirects to '404 page not found' error page instead to the statistics page
Summary: IBM StorageSystem redirects to '404 page not found' error page instead to the...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Bipul Adhikari
QA Contact: Prasad Desala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-08 09:08 UTC by Tal Yichye
Modified: 2023-08-09 16:46 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-21 01:04:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Tal Yichye 2022-05-08 09:08:22 UTC
Description of problem (please be detailed as possible and provide log
snippests):
IBM Flashsystem page redirects to '404: Page Not Found' page when trying to navigate through Storage -> Data Foundation -> StorageSystem

Version of all relevant components (if applicable):
OCP 4.10
ODF 4.10.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
yes

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)?
1

Can this issue reproducible?
tes

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Install ODF
2. Creating StorageSystem for IBM Flashsystem
3. Navigate into the Created StorageSystem


Actual results:
redirects to '404: Page Not Found' page

Expected results:
Open the statistics page for the created StorageSystem

Additional info:

Comment 2 Bipul Adhikari 2022-05-10 08:05:50 UTC
This is due to SDK version mismatch with the IBM Console UI plugin. I had stated in a mail earlier that IBM needs to upgrade it's dependencies for 4.10 and also maintain a compatibility branch for it to work with OCP 4.10 some of the components have been deprecated and hence new components need to be used. 

This was very likely to happen as we were using internal SDK from day 1 and SDK support was not guaranteed and we were explicit about this fact.

Please see https://github.com/red-hat-storage/odf-console/blob/release-4.10/package.json#L50-L53 and upgrade the package version accordingly. (You can ignore packages that is irrelevant)

Comment 3 Alon Firestein 2022-05-11 09:02:30 UTC
We made the necessary changes that were required to upgrade the dependencies that you notified us about.
Unfortunately it fails and we were unable to solve the issue and figure out the reason.
Any chance you could take a look at the error below and let me know if you have any insight.
Thank you very much


Step 5/11 : RUN yarn build
 ---> Running in 7975229873d9
yarn run v1.22.5
$ yarn clean && NODE_ENV=production yarn ts-node ./node_modules/.bin/webpack && yarn locales
$ rm -rf ./dist
$ ts-node -O '{"module":"commonjs"}' -I '/node_modules/(?!(@openshift-console)/)/' ./node_modules/.bin/webpack
(node:55) Warning: Accessing non-existent property 'getOptionValue' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:55) Warning: Accessing non-existent property 'getOptionValue' of module exports inside circular dependency
[webpack-cli] RangeError: Maximum call stack size exceeded
    at Object.getDeclaredExpandoInitializer (/usr/src/app/node_modules/typescript/lib/typescript.js:14427:43)
    at getExpandoSymbol (/usr/src/app/node_modules/typescript/lib/typescript.js:36775:60)
    at getTypeReferenceType (/usr/src/app/node_modules/typescript/lib/typescript.js:44278:22)
    at getTypeFromJSDocValueReference (/usr/src/app/node_modules/typescript/lib/typescript.js:44329:36)
    at getTypeReferenceType (/usr/src/app/node_modules/typescript/lib/typescript.js:44293:33)
    at getTypeFromJSDocValueReference (/usr/src/app/node_modules/typescript/lib/typescript.js:44329:36)
    at getTypeReferenceType (/usr/src/app/node_modules/typescript/lib/typescript.js:44293:33)
    at getTypeFromJSDocValueReference (/usr/src/app/node_modules/typescript/lib/typescript.js:44329:36)
    at getTypeReferenceType (/usr/src/app/node_modules/typescript/lib/typescript.js:44293:33)
    at getTypeFromJSDocValueReference (/usr/src/app/node_modules/typescript/lib/typescript.js:44329:36)
error Command failed with exit code 2.

Comment 4 Tal Yichye 2022-05-18 12:33:35 UTC
Hi,

We are not sure the 404 error is relevant to the SDK packages.
We succeeded to load the IBM Flashsystem page while using the old IBM ODF console image (which contains the old packages), so maybe there is another issue.
The following error appears on the openshift console pod - 

E0518 12:19:05.854517       1 handlers.go:165] GET request for "ibm-storage-odf-plugin" plugin failed: Get "https://ibm-odf-console-service.openshift-storage.svc.cluster.local:9003/locales/en/plugin__ibm-storage-odf-plugin.json": http: server gave HTTP response to HTTPS client

do you have any suggestion?

Thanks

Comment 6 Tal Yichye 2022-06-20 15:35:53 UTC
Hi, 
The issue is fixed. You can close this ticket, Thanks.


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