Bug 2082028 - UI does not have the option to configure capacity, security and networks,etc. during storagesystem creation
Summary: UI does not have the option to configure capacity, security and networks,etc....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.11.0
Assignee: Sanjal Katiyar
QA Contact: Rachael
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-05 08:56 UTC by Rachael
Modified: 2023-08-09 17:00 UTC (History)
9 users (show)

Fixed In Version: 4.11.0-66
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-24 13:51:29 UTC
Embargoed:


Attachments (Terms of Use)
storagesystem creation page (126.80 KB, image/png)
2022-05-05 08:56 UTC, Rachael
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-operator pull 211 0 None open console: update compatibility support matrix for 4.11 2022-05-06 11:55:55 UTC

Description Rachael 2022-05-05 08:56:01 UTC
Created attachment 1877280 [details]
storagesystem creation page

Created attachment 1877280 [details]
storagesystem creation page

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

With OCP and ODF 4.11, after the ODF operator is installed, when the option to create a storagesystem is selected, the UI shows a single form view that does not have the option to select capacity and nodes or configure the security and network related configurations, etc. which were available in the previous versions of ODF. The storagesystem creation does not succeed in this case.

 
Version of all relevant components (if applicable):
---------------------------------------------------
OCP: 4.11.0-0.nightly-2022-05-04-214114
ODF: odf-operator.v4.11.0   full_version=4.11.0-61


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
---------------------------------------------------
Yes, deployment of ODF fails from UI


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

Pasting the workaround from the chat:

Patch the spec.service.basePath from /compatibility/ to / 

apiVersion: console.openshift.io/v1alpha1
kind: ConsolePlugin
metadata:
  name: odf-console
spec:
  displayName: ODF Plugin
  service:
    basePath: /
    name: odf-console-service
    namespace: openshift-storage
    port: 9001


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?
----------------------------
Yes

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

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

Steps to Reproduce:
-------------------
1. Install OCP 4.11
2. Install the ODF 4.11 operator
3. Once the operator is installed, create the storagesystem


Actual results:
---------------
There are no options to select the capacity and nodes for the ODF cluster or configure the security and network configurations.


Expected results:
-----------------
The options mentioned above should be available, as in the previous versions of ODF

Comment 8 errata-xmlrpc 2022-08-24 13:51:29 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.