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:
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.
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.
Ankush, is this already fixed?
This needs to be fixed from OCS-operator. https://github.com/openshift/ocs-operator/issues/756 The UI part is already fixed.
https://github.com/openshift/ocs-operator/issues/756 is targeted for 4.7
Fixed by https://github.com/openshift/ocs-operator/pull/907.
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.
QE will test that during OCS operation installation process, create StorageCluster button is shown so that one can continue with creating storage cluster directly.
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": {} } ] } } ]
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