Bug 1582465

Summary: Incorrect infotip for "Ready to Use" text in the WA Clusters interface
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rakesh <rghatvis>
Component: web-admin-tendrl-uiAssignee: Neha Gupta <negupta>
Status: CLOSED ERRATA QA Contact: Daniel Horák <dahorak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: dahorak, julim, nthomas, rcyriac, rghatvis, rhs-bugs, sankarshan
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 07:07:10 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: 1596660    
Bug Blocks: 1503137    
Attachments:
Description Flags
infotip: Import Failed
none
infotip: Import Passed
none
infotip: Unmanage Failed
none
infotip: Expand Failed
none
infotip: Expand Failed - updated content none

Comment 4 Neha Gupta 2018-05-28 10:59:18 UTC
@ju We can show this "If un-manage fails, resolve the issue and then try un-manage cluster again" tooltip text for only "Unmanage Failed" description and for "Ready to Use", can show "The cluster is successfully imported for viewing monitoring data and metrics". Also, do we need to show tooltip for all other description like Import failed, Expansion failed etc?

Comment 5 Ju Lim 2018-05-29 13:50:57 UTC
+1 on showing tooltips with more details in context to what the message shows.



When unmanage fails, infotip to show "If unmanage fails, resolve the issue and then try unmanage cluster again."



For Ready to Use, infotip to show "The cluster is successfully imported for viewing monitoring data and metrics."



When Import fails, infotip to show "If import cluster fails, resolve the issue before performing an unmanage cluster and then import cluster."



If Expand cluster fails, infotip to show "If cluster expansion fails, check that tendrl-ansible ran without issues and that agents are properly configured."





@rghatvis Please feel free to comment / modify the infotips.

Comment 6 Rakesh 2018-05-31 07:51:46 UTC
Ju, nice suggestions. I just have some minor tweaks. 


(In reply to Ju Lim from comment #5)
> +1 on showing tooltips with more details in context to what the message
> shows.
> 
> 
> 
> When unmanage fails, infotip to show "If unmanage fails, resolve the issue
> and then try unmanage cluster again."

Remove the adverb "then" and modify to: 
"If unmanage fails, resolve the issue and reinitiate unmanage cluster."
> 
> 
> 
> For Ready to Use, infotip to show "The cluster is successfully imported for
> viewing monitoring data and metrics."
LGTM

> 
> 
> 
> When Import fails, infotip to show "If import cluster fails, resolve the
> issue before performing an unmanage cluster and then import cluster."

Modifty to:
"If import cluster fails, resolve the issue before performing an unmanage cluster and reinitiate import."

> 
> 
> 
> If Expand cluster fails, infotip to show "If cluster expansion fails, check
> that tendrl-ansible ran without issues and that agents are properly
> configured."

Modify to:
"If cluster expansion fails, check if tendrl-ansible was executed successfully and ensure the node agents are correctly configured."
> 
> 
> 
> 
> 
> @rghatvis Please feel free to comment / modify the infotips.

Comment 8 Daniel Horák 2018-07-13 14:14:38 UTC
Created attachment 1458736 [details]
infotip: Import Failed

Comment 9 Daniel Horák 2018-07-13 14:15:08 UTC
Created attachment 1458737 [details]
infotip: Import Passed

Comment 10 Daniel Horák 2018-07-13 14:15:45 UTC
Created attachment 1458750 [details]
infotip: Unmanage Failed

Comment 11 Daniel Horák 2018-07-16 07:29:54 UTC
Created attachment 1459058 [details]
infotip: Expand Failed

Comment 12 Daniel Horák 2018-07-16 07:49:43 UTC
All four infotips:
* Import Passed -  attachment 1458737 [details]
* Import Failed -  attachment 1458736 [details]
* Unmanage Failed - attachment 1458750 [details] and
* Expand Failed - attachment 1459058 [details]
are correct from the point of view, that they correspond to the suggestions
from Comment 6.

But the last one for "Failed Expand" is not correct from the content point
of view:
> If cluster expansion fails, check if tendrl-ansible was executed
> successfully and ensure the node agents are correctly configured.

There is no information what to do next, to fix the state (once you resolve
the root cause of the failure).

This issue was described with more details in Bug 1596655 and corresponding
Doc bug 1596660.

Once the correct steps will be at least documented (Bug 1596660), we should
review the infotip covered by this bug and accordingly update it.

>> ASSIGNED

Comment 13 Nishanth Thomas 2018-07-16 09:56:08 UTC
What is your expectation here?

Comment 14 Daniel Horák 2018-07-16 09:59:24 UTC
It depends on the resolution of Doc bug 1596660 (or Bug 1596655, if it will be part of the upcoming release).

Until that, it's not possible to decide what should be written in the infotip.

Comment 15 Neha Gupta 2018-08-01 14:57:32 UTC
@dahorak Bug bz#1596655 is resolved and UI do allows to trigger expand flow, if expansion fails with the infotip as "If cluster expansion fails, check if tendrl-ansible was executed successfully and ensure the node agents are correctly configured.  If cluster expansion failed due to errors, resolve the errors on affected nodes and re-initiate the Expand Cluster action." for "Expand Failed".

Comment 16 Daniel Horák 2018-08-16 06:48:32 UTC
Created attachment 1476364 [details]
infotip: Expand Failed - updated content

Comment 17 Daniel Horák 2018-08-16 06:52:02 UTC
The infotip for Failed Expand was updated accordingly to bug 1596655 comment 7.
See attachment 1476364 [details].

Version: tendrl-ui-1.6.3-10.el7rhgs.noarch

Comment 18 Daniel Horák 2018-08-16 06:53:08 UTC
Verifying based on comment 12 and comment 17.

>> VERIFIED

Comment 20 errata-xmlrpc 2018-09-04 07:07:10 UTC
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