Description of problem (please be detailed as possible and provide log snippests): For Providers under StorageClients page col-2 should have storageclient cluster name and in brackets the cluster id. Currently column 2 shows the cluster id. → oc get storageconsumer -n openshift-storage NAME AGE storageconsumer-4f974f42-2301-460a-90a5-2607cabea062 3m42s storageconsumer-9fd24554-9ba3-49cf-b74d-6b756c8d7d90 16h → oc get storageconsumer storageconsumer-4f974f42-2301-460a-90a5-2607cabea062 -n openshift-storage -o yaml apiVersion: ocs.openshift.io/v1alpha1 kind: StorageConsumer metadata: annotations: ocs.openshift.io/provider-onboarding-ticket: eyJpZCI6Ijg5ZDBlY2E1LTg5ZDItNDdlYy04MzgyLTVmYjNhYWY5NGI3MCIsImV4cGlyYXRpb25EYXRlIjoiMTcxNTg1NTQ2OSJ9.YxF/RLXFs8ARsh2g/qaswjze1tGCaOMJdLTxL9j1/ejI/swNi0/9O6WVvZEXuZ2fVM+1Zmlm3/8RF5H70uwLMDM+TVnnCIQuw+Qiz0pJwzIF6RBfTz8ZyfUyzQrGYx88lC9qFhHd3C5klrlesza8qyhDLsPSN4G3v/Rg7h2zBf5GELdVDa1gE/uXtqVf8M71LxGGtQufLn0I5ZdR3MmfF8ULEZftbnOToCh3/gUBm/Gfz5zjm9/YIep/PjxyIeQ+RS2Jf1NRmvyTmy0p3Couie3Jm+fBs/qAUBm8sAp3KkDcBl6IamR/Hes2IkLA62kEPC6HyKNjVWcIBe9rne5AeSiOGABMmam5TjqYUHKOmmA1x06MuX0zrysXEz42wLBWJgAaGBPx/TzhwGRWx2ZGGhBAkDN7n7LmgBbYg/KwuY/o4V0m6XiURc/ZQ5/jgFWfsv6XJUTxI6vbtNSI3K1fPU/0leknlWcbEY2Fk9btRlhXSOLolJ2cP2nHbi4biuvRuwturFU3tFwUBsaG2nRt+6FmhM47fheFtXg/SYeaLLrtgKoeGrM7GcIj4ie5GyIVJ0VNfKvl25JtuftRxIfiFiMpEiQlsiiWZVB1PDkLuiX7zSgISi9R0Jad0ISqBfl7dDpJRKkoXO7/+aahJ41q69wMuEVJ0w6WoPZjS6Bazts= creationTimestamp: "2024-05-14T10:31:32Z" generation: 2 name: storageconsumer-4f974f42-2301-460a-90a5-2607cabea062 namespace: openshift-storage resourceVersion: "776018" uid: 6f133d76-2cbb-431f-9df5-2fc95bb30171 spec: enable: true status: cephResources: - kind: CephClient name: 57485a74f3e950d05c1b57c1be93a3ec status: Ready client: clusterId: 4f974f42-2301-460a-90a5-2607cabea062 clusterName: ibm-baremetal2 name: storage-client-provider-bm3 operatorVersion: 4.16.0-96.stable platformVersion: 4.16.0-ec.5 lastHeartbeat: "2024-05-14T10:35:01Z" state: Ready Version of all relevant components (if applicable): ODF: 4.16.0-96 stable Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No 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? Yes Can this issue reproduce from the UI? It is UI issue If this is a regression, please provide more details to justify this: NA Steps to Reproduce: 1. Create a provider/client configuration following the docs [1] and [2] 2. Install the ocs-client-operator from the CLI [yaml at [3] as it is not listed under the Operator Hub 3. Check the Storage->StorageClients page. Screenshot attached [1] https://docs.google.com/document/d/1uVjzJQFv_t1Fymb-hgMhNd6pve8fkbrxp1TadU5wv9I/edit?pli=1 [2] https://docs.google.com/document/d/1RfDNQi4B3x4kv9PXx2lqGSD2V2UGideTCIXqLYJFg0Y/edit?pli=1#heading=h.bebinah79b8e Actual results: For Providers under StorageClients page col-2 shows the cluster id. Expected results: For Providers under StorageClients page col-2 should have storageclient cluster name and in brackets the cluster id. Additional info:
As per the designs the current UI view is as per the designs made by the UXD team. Design link: https://www.figma.com/design/Afl7ntvufZTshGyuX701u7/Provider-consumer?node-id=0-1&t=UMz6SS8ere8RUehh-0 These are coming as enhancement at a later part requires changes on the UX designs as well. Marking it as a non blocker.
(In reply to Bipul Adhikari from comment #6) > As per the designs the current UI view is as per the designs made by the UXD > team. Design link: > https://www.figma.com/design/Afl7ntvufZTshGyuX701u7/Provider-consumer?node- > id=0-1&t=UMz6SS8ere8RUehh-0 > > These are coming as enhancement at a later part requires changes on the UX > designs as well. Marking it as a non blocker. Ack.. Based on discussions in https://ibm-systems-storage.slack.com/archives/C06EPQRBM36/p1715710923045299, moving it out to 4.17 As a stretch goal, we can take it in 4.16.z
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.17.0 Security, Enhancement, & Bug Fix 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-2024:8676