Bug 1435083 - openshift users encountered confirmation "Apply these filters?" when switching between index list populated in the left panel on kibana
Summary: openshift users encountered confirmation "Apply these filters?" when switchin...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.4.z
Assignee: Rich Megginson
QA Contact: Junqi Zhao
URL:
Whiteboard:
: 1444106 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-23 05:23 UTC by Junqi Zhao
Modified: 2020-12-14 08:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: 3.4 upgraded the Elasticsearch schema to the common data model but did not upgrade the Kibana schema. Consequence: There were strange errors like "Apply these filters?" in Kibana. Fix: The correct schema was added to Kibana for the common data model. Result: Kibana works as expected.
Clone Of:
Environment:
Last Closed: 2017-10-25 13:00:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Apply these filters message (144.53 KB, image/png)
2017-03-23 05:23 UTC, Junqi Zhao
no flags Details
kibana ui, tested with the latest images (139.69 KB, image/png)
2017-05-09 01:39 UTC, Junqi Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3049 0 normal SHIPPED_LIVE OpenShift Container Platform 3.6, 3.5, and 3.4 bug fix and enhancement update 2017-10-25 15:57:15 UTC

Description Junqi Zhao 2017-03-23 05:23:11 UTC
Created attachment 1265599 [details]
Apply these filters message

Description of problem:
Openshift users encountered unexpected confirmation "Apply these filters?" when switching between index list populated in the left panel on kibana.

Same issue with https://bugzilla.redhat.com/show_bug.cgi?id=1388031 and https://bugzilla.redhat.com/show_bug.cgi?id=1426061, and it has been fixed on logging 3.5.0

Version-Release number of selected component (if applicable):
ops registry:
openshift3/logging-elasticsearch   3.4.1               246537fe4546        8 hours ago         399.2 MB
openshift3/logging-deployer        3.4.1               0eeabd69aa6d        37 hours ago        889.5 MB
openshift3/logging-auth-proxy      3.4.1               d85303b2c262        2 weeks ago         219.8 MB
openshift3/logging-kibana          3.4.1               03900b0b9416        2 weeks ago         339.1 MB
openshift3/logging-fluentd         3.4.1               e4b97776c79b        2 weeks ago         233 MB
openshift3/logging-curator         3.4.1               091de35492d6        2 weeks ago         244.3 MB

Steps to Reproduce:
1.Deploy logging 3.4.1
2.Wait until EFK stacks are all running, login kibana UI
3.Switch between different indices from the left panel

Actual results:
Encounter unexpected confirmation "Apply these filters?", log entries didn't display

Expected results:
Should not encounter unexpected confirmation "Apply these filters?", log entries should display

Additional info:
The workaround is effective: go to the Settings tab and select the index you want view, then go back to the Discover tab and refresh the page.

Comment 2 Rich Megginson 2017-04-11 19:53:48 UTC
Marc, the bz bot gives an auto ack for pm - you should consider giving a real pm ack for this issue considering how many customers are hitting this.

Comment 3 Peter Portante 2017-04-14 10:47:15 UTC
Do need this BZ and https://bugzilla.redhat.com/show_bug.cgi?id=1388031?

Comment 4 Jeff Cantrill 2017-04-18 16:01:19 UTC
@Peter,

I think this issue will address 3.4 since the other from #3 was targeted 3.5.  I believe Rich has backported this in https://github.com/openshift/origin-aggregated-logging/pull/380 which pulls in: https://github.com/fabric8io/openshift-elasticsearch-plugin/pull/71

Comment 5 Rich Megginson 2017-05-05 15:20:47 UTC
The fix is in the latest images:

logging-auth-proxy-docker-3.4.1-11        rhaos-3.4-rhel-7-candidate  osbs
logging-curator-docker-3.4.1-8            rhaos-3.4-rhel-7-candidate  osbs
logging-deployment-docker-v3.4.1.20-1     rhaos-3.4-rhel-7-candidate  osbs
logging-elasticsearch-docker-3.4.1-21     rhaos-3.4-rhel-7-candidate  osbs
logging-fluentd-docker-3.4.1-8            rhaos-3.4-rhel-7-candidate  osbs
logging-kibana-docker-3.4.1-9             rhaos-3.4-rhel-7-candidate  osbs

or later

Comment 6 Rich Megginson 2017-05-05 15:52:46 UTC
There is another bz for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1444106  - which is targeted for 3.4 backport.

For this 1435083 bz, what release are we targeting?

Comment 7 Junqi Zhao 2017-05-09 01:37:51 UTC
There is one same defect: https://bugzilla.redhat.com/show_bug.cgi?id=1444106 and was closed, images details please see https://bugzilla.redhat.com/show_bug.cgi?id=1444106#c10

But I tested with the latest images, this error is reproduced, see the attached picture.

docker images | grep logging
openshift3/logging-deployer        3.4.1               dcee53833a87        28 hours ago        856.6 MB
openshift3/logging-kibana          3.4.1               e7b6eb3c6d3c        3 days ago          339.3 MB
openshift3/logging-elasticsearch   3.4.1               fab3ad9b2410        3 days ago          399.4 MB
openshift3/logging-fluentd         3.4.1               10c6287124fc        3 days ago          232.7 MB
openshift3/logging-curator         3.4.1               e8b1bbdfa30f        3 days ago          244.5 MB
openshift3/logging-auth-proxy      3.4.1               f2750505bbf8        10 days ago         215 MB

Comment 8 Junqi Zhao 2017-05-09 01:39:19 UTC
Created attachment 1277197 [details]
kibana ui, tested with the latest images

Comment 9 Rich Megginson 2017-05-09 01:51:29 UTC
The only thing I can think of is that some earlier image was tagged with 3.4.1, replacing the fix.  I've asked Jeff and Troy what can be done about this.

Comment 10 Xiaoli Tian 2017-05-11 02:10:47 UTC
*** Bug 1444106 has been marked as a duplicate of this bug. ***

Comment 11 Junqi Zhao 2017-05-18 01:33:37 UTC
The latest image for elasticsearch is logging-elasticsearch:3.4.1-26, tested with this image, this issue is fixed.

Please change the Status to ON_QA, so I can close it. 

# docker images | grep logging
/openshift3/logging-deployer        3.4.1               50df91cebdd9        37 hours ago        856.6 MB
/openshift3/logging-fluentd         3.4.1               72e1937f640d        2 days ago          233.2 MB
/openshift3/logging-curator         3.4.1               10d5d588dce7        2 days ago          245 MB
/openshift3/logging-kibana          3.4.1               6896fc60e73f        2 days ago          338.8 MB
/openshift3/logging-elasticsearch   3.4.1               7ccfb575c46c        2 days ago          399.6 MB
/openshift3/logging-elasticsearch   3.4.1-26            7ccfb575c46c        2 days ago          399.6 MB
/openshift3/logging-auth-proxy      3.4.1               3493cb418daf        2 days ago          215.3 MB

Comment 12 Junqi Zhao 2017-05-18 02:16:07 UTC
Set it to VERIFIED based on Comment 11

Comment 14 errata-xmlrpc 2017-10-25 13:00:48 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/RHBA-2017:3049


Note You need to log in before you can comment on or make changes to this bug.