Bug 2070037

Summary: ODF console integration into OCP web console is missing / ODF console web page does not load
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Dirk Haubenreisser <dhaubenr>
Component: management-consoleAssignee: Nishanth Thomas <nthomas>
Status: CLOSED NOTABUG QA Contact: Prasad Desala <tdesala>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.10CC: badhikar, jefbrown, madam, nthomas, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-30 13:11:55 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
ODF console integration missing / broken (screenshot) none

Description Dirk Haubenreisser 2022-03-30 10:53:21 UTC
Created attachment 1869339 [details]
ODF console integration missing / broken (screenshot)

Description of problem (please be detailed as possible and provide log
snippests):


The ODF console integration is missing from the OCP web console. While there should be a 'Data Foundation' menu entry in the web console 'Storage' submenu, there is none. This is despite the ODF console plugin being enabled for the ODF operator and the odf-console pod running just fine in 'openshift-storage' namespace.

When trying to navigate to the ODF console endpoint directly the web page doesn't load (all I get is the never-ending loading ellipses).

This is happening on all of my test cluster on s390x (using hypervisors z/VM and KVM) with the following ODF build installed:

rp_ocp_version: 4.9
rp_ocs_version: 4.10
rp_ocs_registry_image: quay.io/rhceph-dev/ocs-registry:latest-stable-4.10.0
rp_ocs_registry_tag: latest-stable-4.10.0
rp_ocs_build: 4.10.0-210


Version of all relevant components (if applicable):

rp_ocp_version: 4.9
rp_ocs_version: 4.10
rp_ocs_registry_image: quay.io/rhceph-dev/ocs-registry:latest-stable-4.10.0
rp_ocs_registry_tag: latest-stable-4.10.0
rp_ocs_build: 4.10.0-210


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

Yes, the ODF console integration is vital to be able to work with ODF from the web console. Interaction with ODF via CLI (e.g. 'oc') is not impacted.


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 - very simple


Can this issue reproducible?

Yes. The issue is present on all test clusters installed with the same ODF build.


Can this issue reproduce from the UI?

Yes.

Comment 2 Dirk Haubenreisser 2022-03-30 11:26:01 UTC
Fwiw, this issue seems to be present on ODF installations on top of **OCP 4.9** (OCP 4.9.25 in my case) only. Other users reported that ODF 4.10 on OCP 4.10 does not exhibit this issue, meaning that the ODF console works just fine on OCP 4.10.

Comment 3 Bipul Adhikari 2022-03-30 13:11:55 UTC
OCP 4.9 will not show ODF 4.10 in Operator Hub. You are probably manually adding the subscription to ODF 4.10.
Our compatibility matrix is ODF 4.x support OCP 4.x and 4.(x+1). So ODF 4.10 will work with OCP 4.10 and 4.11 and not with OCP 4.9.