Bug 1866301

Summary: [RHOCS Usability Study][Installation] “Create storage cluster” should be a part of the installation flow or need to be emphasized as a crucial step.
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Harish NV Rao <hnallurv>
Component: ocs-operatorAssignee: Neha Berry <nberry>
Status: CLOSED ERRATA QA Contact: Neha Berry <nberry>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: anbehl, aos-bugs, badhikar, bkunal, erich, jarrpa, madam, mbukatov, muagarwa, nberry, nthomas, ocs-bugs, sostapov, uchapaga
Target Milestone: ---Keywords: AutomationBackLog, UpcomingSprint, UsabilityStudyPriority
Target Release: OCS 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-19 09:14:56 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
screencast for verification none

Description Harish NV Rao 2020-08-05 10:40:45 UTC
Description of problem:

It’s not easy for the users to come to know that they have to create a storage cluster after installing the operators. Either “Create storage cluster” should be a part of the installation flow or need to be emphasized as a crucial step.

UX issue severity level: 2-High (refer below mentioned doc for severity levels)

This BZ is being filed based on the Usability study conducted on RHOCS during July 2020. A complete report on this Usability study can be found here: https://docs.google.com/presentation/d/1w65Rl2ZsTew-TIqgKUaZ9Y-1DmG1Z4Y59sYQjYC_mMM/edit#slide=id.g547716335e_0_260


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Bipul Adhikari 2020-08-07 05:52:13 UTC
OCP 4.6 should allow up to direct the user towards the Storage Cluster Creation. To be taken as a feature work in 4.7.

Comment 4 Ankush Behl 2020-09-22 15:26:22 UTC
The label needs to be added from the CSV to make this available from the UI to work the feature is already part of 4.6 from console UI.

Comment 6 Mudit Agarwal 2020-10-09 12:35:35 UTC
Ankush, is this already fixed?

Comment 7 Ankush Behl 2020-10-12 06:00:06 UTC
This needs to be fixed from OCS-operator. 
https://github.com/openshift/ocs-operator/issues/756

The UI part is already fixed.

Comment 8 Mudit Agarwal 2020-10-12 06:02:16 UTC
https://github.com/openshift/ocs-operator/issues/756 is targeted for 4.7

Comment 9 umanga 2021-01-15 16:13:24 UTC
Fixed by https://github.com/openshift/ocs-operator/pull/907.

Comment 10 Jose A. Rivera 2021-01-20 14:43:13 UTC
The PR above makes use of a new feature in the OCP Console that slightly changes the workflow to show a prompt to create a StorageCluster and a button that allows them to do so directly. I believe this improves the workflow in the same way this BZ was hoping to do.

Comment 11 Martin Bukatovic 2021-01-20 22:17:37 UTC
QE will test that during OCS operation installation process, create StorageCluster button is shown so that one can continue with creating storage cluster directly.

Comment 14 Neha Berry 2021-01-22 09:12:55 UTC
Created attachment 1749679 [details]
screencast for verification

(In reply to Martin Bukatovic from comment #11)
> QE will test that during OCS operation installation process, create
> StorageCluster button is shown so that one can continue with creating
> storage cluster directly.

Verified the fix in UI and also checked the ocs-operator.v4.7.0-237.ci.yaml for the newly added annotations (https://github.com/openshift/ocs-operator/pull/907/files)

OCS = ocs-operator.v4.7.0-237.ci

OCP = 4.7.0-0.nightly-2021-01-19-095812

Steps Performed:
=====================
1. Created the internal build for 4.7.0-231.ci in Operator hub (using deploy-wih-olm.yaml)
2. Selected the OCS operator from OperatorHub and Clicked on Install 
3. On "Install Operator" page, selected the default options and clicked on Install
4. Window [1] came up and once the operator is installed and all 4 operator pods are in Running state, the option for Create Storagecluster becomes active.


Added screencast of the flow.

Outputs for reference
------------------------
$ oc get csv
NAME                         DISPLAY                       VERSION        REPLACES   PHASE
ocs-operator.v4.7.0-237.ci   OpenShift Container Storage   4.7.0-237.ci              Succeeded

=======PODS ======
NAME                                    READY   STATUS    RESTARTS   AGE   IP             NODE        NOMINATED NODE   READINESS GATES
noobaa-operator-668495668b-srrth        1/1     Running   0          67s   10.128.2.18    compute-5   <none>           <none>
ocs-metrics-exporter-69fc64df49-v42sq   1/1     Running   0          67s   10.130.2.10    compute-3   <none>           <none>
ocs-operator-6d95db8cf4-wb64s           1/1     Running   0          67s   10.131.0.245   compute-2   <none>           <none>
rook-ceph-operator-6658b8b7-7pqcm       1/1     Running   0          67s   10.128.4.12    compute-0   <none>           <none>
--------------

-------------------------------------

$ oc get csv ocs-operator.v4.7.0-237.ci -o yaml


apiVersion: v1
items:
- apiVersion: operators.coreos.com/v1alpha1
  kind: ClusterServiceVersion
  metadata:
    annotations:
      alm-examples: |2-

        [
            {
                "apiVersion": "ocs.openshift.io/v1",
                "kind": "StorageCluster",
                "metadata": {
                    "name": "example-storagecluster",
                    "namespace": "openshift-storage"
                },
                "spec": {
                    "manageNodes": false,
                    "monPVCTemplate": {
                        "spec": {
                            "accessModes": [
                                "ReadWriteOnce"
                            ],
                            "resources": {
                                "requests": {
                                    "storage": "10Gi"
                                }
                            },
                            "storageClassName": "gp2"
                        }
                    },
                    "storageDeviceSets": [
                        {
                            "count": 3,
                            "dataPVCTemplate": {
                                "spec": {
                                    "accessModes": [
                                        "ReadWriteOnce"
                                    ],
                                    "resources": {
                                        "requests": {
                                            "storage": "1Ti"
                                        }
                                    },
                                    "storageClassName": "gp2",
                                    "volumeMode": "Block"
                                }
                            },
                            "name": "example-deviceset",
                            "placement": {},
                            "portable": true,
                            "resources": {}
                        }
                    ]
                }
            }
        ]

Comment 18 errata-xmlrpc 2021-05-19 09:14: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 (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement 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-2021:2041