Description of problem: I encountered 4 issues while testing the Multus UX usability. Most of them seem to be "by design" but IMO we should pay attention to the usability part again. 1. While there is only 1 NAD, when prompt to select the NICs, there are 2 drop down lists (public & cluster). I would expect to see only 1 drop down and the NAD should be selected automatically. 2. If I have 2 NADs and I select them both in the opposite way (cluster to public and vise versa), my only option to reset them is to change my option to default (SDN) and back to Multus 3. Clicking on the radio button to switch between default (SDN) and Multus clears Multus public & cluster NAD selections. 4. There is only 1 tooltip for both SDN & Multus info. I think it will be better to split it to 2 tooltips aside to each option from the radio buttons. Maybe we can enhance the tooltip information. Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-07-26-182557 How reproducible: 100% Steps to Reproduce: 1. Deploy a new OCP only cluster 2. Create NAD for Multus 3. Install OCS operator 4. Go to Installed Operator -> OpenShift Container Storage -> Create StorageCluster 5. Click on the 2nd step on the left (Security and network) 6. Under "Network", switch to "Custom (Multus)" Actual results: Expected results: 1. The only NAD should be selected automatically. 2. There should be a button/link to clear the selection. 3. Switch between default and custom shouldn't clear the selection. 4. There should be 2 tooltips aside to each network option Additional info:
(In reply to Yosi Ben Shimon from comment #0) > Description of problem: > I encountered 4 issues while testing the Multus UX usability. > Most of them seem to be "by design" but IMO we should pay attention to the > usability part again. > > 1. While there is only 1 NAD, when prompt to select the NICs, there are 2 > drop down lists (public & cluster). I would expect to see only 1 drop down > and the NAD should be selected automatically. Users can proceed with using only one NAD (public or clutser) so we cannot assume which dropdown to show. > > 2. If I have 2 NADs and I select them both in the opposite way (cluster to > public and vise versa), my only option to reset them is to change my option > to default (SDN) and back to Multus Yes this is something I added by design. Usually there are no clear buttons in dropdown menus. So users can only clear their selection by restarting the flow or toggling network connection. > > 3. Clicking on the radio button to switch between default (SDN) and Multus > clears Multus public & cluster NAD selections. This is by design to solve issues mentioned in 3. > > 4. There is only 1 tooltip for both SDN & Multus info. I think it will be > better to split it to 2 tooltips aside to each option from the radio buttons. > Maybe we can enhance the tooltip information. @Yuval WDYT? Should we enhance the tooltips? > > > Version-Release number of selected component (if applicable): > 4.8.0-0.nightly-2021-07-26-182557 > > > How reproducible: > 100% > > Steps to Reproduce: > 1. Deploy a new OCP only cluster > 2. Create NAD for Multus > 3. Install OCS operator > 4. Go to Installed Operator -> OpenShift Container Storage -> Create > StorageCluster > 5. Click on the 2nd step on the left (Security and network) > 6. Under "Network", switch to "Custom (Multus)" > > Actual results: > > > Expected results: > 1. The only NAD should be selected automatically. > > 2. There should be a button/link to clear the selection. > > 3. Switch between default and custom shouldn't clear the selection. > > 4. There should be 2 tooltips aside to each network option > > > Additional info:
will be fixed in ODF 4.13
@skatiyar Need steps for verification. Out of 4 issue which issue is fixed?
Hi Avdhoot, I will let assignee of the BZ to provide the details: @tjeyasin
We fixed the 4th Issue
There are 2 tooltips present aside to each network option. Please find attached screenshot OCP- 4.13.0 ODF- 4.13.0-170 Hence marking it as verified.
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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and 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/RHBA-2023:3742