Bug 1395079

Summary: Hover at Tooltip show info twice when ConfigMap is shown in Pod Environment
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: bpeterse
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: medium    
Version: 3.4.0CC: aos-bugs, chali, etrott, jforrest, jokerman, mmccomas, rhamilto, tdawson, xxia
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously while hovering over the help icon for a configmap in the environment editor for a pod, the help text bubble would appear twice, side by side, revealing duplicate help text. Now a single tooltip will show the appropriate help text.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-10 05:15:47 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:
Attachments:
Description Flags
ShowInfoTwice
none
Common_twice_display none

Description Yadan Pei 2016-11-15 05:34:43 UTC 
Description of problem:
When a pod consume the configmap value, configmap value will be shown in Pod Environment tab, when hover at the question mark ?, it will show info twice

Version-Release number of selected component (if applicable):
v3.4.0.26

How reproducible:
Always

Steps to Reproduce:
1.Create ConfigMap and a Pod that consume the configmap value
# oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/configmap/configmap.yaml
# oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/configmap/pod-configmap-command.yaml
2.Login to web console
3.Go to Pods page
4.Check Pods Environment tab

Actual results:
4. SPECIAL_LEVEL_KEY -> Set to the key special.how in config map special-config
SPECIAL_TYPE_KEY -> Set to the key special.type in config map special-config
When hover at the question mark "?", it will show info twice:
This is a referenced value that will be generated when a container is created.  On running pods you can check the resolved values by going to the Terminal tab and echoing the environment variable.


Expected results:
4.Message should be shown only once, no need to show twice

Additional info:
Comment 1 Yadan Pei 2016-11-15 05:35:14 UTC 
Created attachment 1220691 [details]
ShowInfoTwice
Comment 2 Xingxing Xia 2016-11-16 07:00:32 UTC 
Created attachment 1221041 [details]
Common_twice_display

Found the twice display issue on other places, e.g, input invalid env var name on BC page, DC page, Crate From Image page, it shows 'Please enter a valid key" and '?' icon. Hovering upon the '?' icon, the issue occurs, see attachment Common_twice_display
Comment 3 Samuel Padgett 2016-11-16 11:48:07 UTC 
I haven't been able to reproduce, but it seems specific to the key value editor. What browser are you using?
Comment 4 Xingxing Xia 2016-11-17 10:09:16 UTC 
Both comment 0 and comment 2 are reproduced on both Firefox and Chrome for me. My Firefox version is 49, Chrome version is 53. Didn't check other browsers yet.
Comment 5 Jessica Forrester 2017-02-20 18:25:50 UTC 
The second one is the browser's title text popup, its not a second bootstrap tooltip.  If you hover over the (?) long enough you will see both.
Comment 6 Robb Hamilton 2017-02-20 19:09:04 UTC 
Fixed in https://github.com/openshift/origin-web-console/pull/1090

Waiting for merge queue to open before moving to modified.
Comment 7 Jessica Forrester 2017-03-03 18:57:08 UTC 
*** Bug 1428996 has been marked as a duplicate of this bug. ***
Comment 8 Troy Dawson 2017-04-11 20:42:55 UTC 
This has been merged into ocp and is in OCP v3.6.27 or newer.
Comment 10 lichao 2017-04-12 10:00:05 UTC 
Description and comment 2 have fixed in OCP v3.6.27
Comment 12 errata-xmlrpc 2017-08-10 05:15:47 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/RHEA-2017:1716