Bug 1588650
Summary: | discovered host(s) section in import cluster screen is slightly inconsistent/misleading | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Martin Bukatovic <mbukatov> |
Component: | web-admin-tendrl-ui | Assignee: | Neha Gupta <negupta> |
Status: | CLOSED ERRATA | QA Contact: | Martin Bukatovic <mbukatov> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.4 | CC: | julim, nthomas, rhs-bugs, sankarshan |
Target Milestone: | --- | ||
Target Release: | RHGS 3.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tendrl-ui-1.6.3-4.el7rhgs | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-09-04 07:07:28 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1503137 | ||
Attachments: |
Description
Martin Bukatovic
2018-06-07 16:45:43 UTC
Linking related BZ: 1584660 Question for Ju: do you think that we need to do anything besides allowing import with empty host list? Created attachment 1448787 [details]
screenshot 1: import cluster screen
Created attachment 1448788 [details]
screenshot 2: import cluster screen when filtering some hosts
Created attachment 1448789 [details]
screenshot 3: import cluster screen when no hosts are shown after filtering
In reviewing the screenshots, I observed the following: (1) 1 or more hosts need to be visible for the "Import" button to be enabled. (2) The filter (to the host table) is for locating a specific host(s) with the host table, but it is not needed for performing the import. (3) It's confusing as user loses context of what the total number of discovered hosts vs. filtered hosts when a filter is applied. E.g. 2 of 10 discovered hosts, whereby 2 hosts filtered out of a total list of 10 discovered hosts. Refer to https://www.patternfly.org/pattern-library/content-views/table-view/ for further information. My recommendations are as follow: (1) Update UI to include the <filtered item count> of <total items> Discovered hosts when filtered is applied. (2) With regards to Import not enabled until all hosts are not filtered. It's behaving the way it should as if we put a filter and let users Import, it can be confusing to users whether all or a subset of nodes are being imported. Hence, my suggestion is to add a validation that provides a message (like you get when you put invalid text in the custom cluster name -- see https://redhat.invisionapp.com/share/8QCOEVEY9#/screens/279647239) so that if there is any filters on the discovered hosts, that the filter has to be cleared or removed before the Import is enabled. E.g. "Review the discovered host list, and ensure there are no filters applied before proceeding with Import." QE team will verify that the Ju's suggestion in comment 6 is implemented. Checking tendrl-ui-1.6.3-4.el7rhgs.noarch When filter for "Discovered Host(s)" is applied, the page reports eg.: > 1 of 4 Discovered - Hosts - where 1 is number of hosts which matches active filters, and 4 is total number of discovered hosts. When the filter matches no hosts, the page works the same as before, shows: > No Hosts Detected This matches the suggestion in comment 6. When one clicks on "Import" button while some filters are active, the error is shown on the top of the page: > Review the discovered host list, and ensure there are no filters applied > before proceeding with Import. This remains on the page even after the filters are removed. I have no problem with that. When the filters are removed, the it's possible to start import again. 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, 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-2018:2616 |