Created attachment 1228017 [details] logout link is missing Description of problem: logout link is missing in kibana UI Discover tab. User only can use logout link under Settings tab Version-Release number of selected component (if applicable): # openshift version openshift v3.4.0.32+d349492 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 How reproducible: Always Steps to Reproduce: 1. Deployed logging stacks. 2. Logging in kibana UI with workaround of Bug 1388031 -"openshift users encountered confirmation "Apply these filters?" when switching between index list populated in the left panel on kibana" 3. Actual results: logout link shold be found in Discover tab. Expected results: logout link is missing in Discover tab. Additional info: I think this issue is caused by the workaround of Bug 1388031, after doing the workaround,logout link is missing in Discover tab, if we refresh the page,the logout link is shown again, see the attached pictures.
I believe https://github.com/openshift/origin-aggregated-logging/pull/306 should fix which pulls in https://github.com/openshift/origin-kibana/pull/25
This update is in the rpm origin-kibana-4.5.1-7.el7
The image with the updated rpm is openshift3/logging-kibana:3.4.0-8 It should be in places that QE can test
Tested on OCP 3.4.0 with the latest kinana image, logout link is shown under Discover tab after doing workaround of Bug 1388031 -"openshift users encountered confirmation "Apply these filters?" when switching between index list populated in the left panel on kibana". Switch between different user project, logout link still can be shown under Discover tab. Set this issue to VERIFIED Image id: openshift3/logging-kibana d5971557d356 openshift3/logging-deployer 157b6a7ac24a openshift3/logging-fluentd 7b11a29c82c1 openshift3/logging-elasticsearch 6716a0ad8b2b openshift3/logging-auth-proxy ec334b0c2669 openshift3/logging-curator 9af78fc06248
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/RHBA-2017:0067