Bug 1430667 - Roll over log entries are visible when openshift_logging_fluentd_journal_read_from_head is default to empty on journald log driver envs
Summary: Roll over log entries are visible when openshift_logging_fluentd_journal_read...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 3.6.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-09 09:22 UTC by Xia Zhao
Modified: 2017-10-25 13:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-10-25 13:00:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
inventory file used for logging deployment to let this bz repro (1.06 KB, text/plain)
2017-03-09 09:22 UTC, Xia 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 Xia Zhao 2017-03-09 09:22:43 UTC
Created attachment 1261478 [details]
inventory file used for logging deployment to let this bz repro

Description of problem:
Created according to discussions in https://bugzilla.redhat.com/show_bug.cgi?id=1426137
Roll over log entries are visible when openshift_logging_fluentd_journal_read_from_head is default to empty on journald log driver envs.
Issue did not repro when openshift_logging_fluentd_journal_read_from_head is not specified.
    
Version-Release number of selected component (if applicable):
openshift-ansible-3.5.28-1.git.0.103513e.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Deploy logging 3.5.0 with ansible scripts ,including this parameter:
openshift_logging_fluentd_use_journal = true
and make sure parameter "openshift_logging_fluentd_journal_read_from_head "is unspecified in the inventory file
2.Tail ES log for namespaces that was created prior to EFK deployments
3.Log in kibana

Actual results:
2.Index mappings was created in ES for namespaces that was created prior to EFK deployments
3.Roll over logs are displayed

Expected results:
2.Index mappings should not be created in ES for namespaces that was created prior to EFK deployments
3.Roll over logs (and indices) should not exist

Additional info:
inventory file used for logging deployment was attached

Comment 1 Peter Portante 2017-05-01 18:40:05 UTC
Is this a problem of seeing duplicate logs in Kibana?  Or are you not expecting to see old logs?

Comment 2 Xia Zhao 2017-05-11 07:10:38 UTC
(In reply to Peter Portante from comment #1)
> Is this a problem of seeing duplicate logs in Kibana?  
No

> Or are you not expecting to see old logs?
Yes

Comment 3 Xia Zhao 2017-07-13 08:33:58 UTC
According to https://bugzilla.redhat.com/show_bug.cgi?id=1426137#c22, I'm considering on adjusting the test scope here, and the situation when openshift_logging_fluentd_journal_read_from_head is not set (default to false) is test passed with 3.6 installer, please feel free to transfer back to ON_QA for closure. Thanks!

Comment 4 Xia Zhao 2017-07-14 08:31:16 UTC
Set to verified according to comment #3.

Image tested with:
logging-fluentd            v3.6                b9eeeec142af        17 hours ago        231.7 MB

# openshift version
openshift v3.6.144
kubernetes v1.6.1+5115d708d7
etcd 3.2.1

ansible version:
openshift-ansible-playbooks-3.6.144-1.git.0.50e12bf.el7.noarch

Comment 6 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.