Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 2004843 [details] image of operator storage system and odf foundation storage system Description of problem (please be detailed as possible and provide log snippests): After installation of internal and external storagesystems under odf-operator only the internal one is shown. Probably due to operator namespace is openshift-storage and external storagesystem is created in another namespace (extended) Version of all relevant components (if applicable): quay.io/rhceph-dev/ocs-registry:4.15.0-88 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No.the external storagesystem can be found under data foundation under storage. Is there any workaround available to the best of your knowledge? Yes 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? 2/2 Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: No Steps to Reproduce: 1. Install OCP cluster 2. Install ODF. 3. Create internal storagesystem 4. Create external storagesystem Actual results: Only internal storagesystem is displayed under the operator although the external one was created also under the operator. The problem probably is due to operator is under namespace openshift-storage and external storagesystem is created in another namespace. Expected results: Both storagesystem should be shown under the operator is it is managing both of them. Additional info:
StorageSystem list page under "OperatorHub > Installed Operators > Provided APIs > StorageSystem" currently belongs to OCP and is a default page which only display resources in the namespaces which are managed by the operator (ODF only manages "openshift-storage"). We do have a project dropdown on the top which get selected to "openshift-storage" by default and thus show only systems in this namespace, so it is kind of working as expected, but could cause confusion for the users. Need to discuss further with the UX team on its impact and decide accordingly on what steps to take. In worst case this behaviour can also be documented for multiple storagecluster use case.
Created attachment 2005259 [details] prossible_ux_flow Hi Eran, IMO we can do either of 2 things (please feel free to add any other suggestion as well, if needed): 1. Consider this a small RFE for 4.15 and add a custom StorageSystem list page to OCP's "OperatorHub > Installed Operators > Provided APIs > StorageSystem" (we can inject existing custom list page that we have under "Storage > Data Foundation > Storage Systems"). UX can look like this attached screenshot (notice 2 radio buttons). 2. Document that OCP's "OperatorHub > Installed Operators > Provided APIs > StorageSystem" page will show list of StorageSystems in the operator namespace only (that's default working of OCP/OLM UI for such operators), if multiple StorageCluster users wants to see entire list they can navigate to "Storage > Data Foundation > Storage Systems". can you please share your opinion on this ??