Bug 1511719 – operations logs lost if no ops cluster and no @OUTPUT label

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1511719 - operations logs lost if no ops cluster and no @OUTPUT label

Summary:	operations logs lost if no ops cluster and no @OUTPUT label

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Logging (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	---
Target Release:	3.7.0
Assigned To:	Rich Megginson
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1512028
	Show dependency tree / graph

Reported:	2017-11-09 19:02 EST by Rich Megginson
Modified:	2017-12-18 08:23 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: When upgrading to a new version of logging, if the deployment does not use a separate OPS logging cluster, and there is no @OUTPUT label in the fluent.conf, fluentd does not know how to route the operations logs. Consequence: The operations logs are not logged. User will see no new operations (.operations.*) logs after the upgrade. Fix: Change the fluentd configuration to correctly handle the case both with and without the @OUTPUT label, and for the OPS and non-OPS cases. Result: Operations logs flow uninterrupted after upgrade.
Story Points:	---
Clone Of:
Clones:	1512028 (view as bug list)
Environment:
Last Closed:	2017-12-18 08:23:56 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	openshift/origin-aggregated-logging/pull/774	None	None	None	2017-11-09 19:03 EST
Red Hat Product Errata	RHBA-2017:3464	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.7 bug fix and enhancement update	2017-12-18 13:22:05 EST

Groups: None (edit)

Description Rich Megginson 2017-11-09 19:02:51 EST

Description of problem:
Deploy logging with no ops cluster and based on 3.6 or an earlier 3.7 pre-release which does not have the @OUTPUT label in fluent.conf

update to a recent fluentd image

no operations logs are stored

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Rich Megginson 2017-11-10 12:20:45 EST

https://github.com/openshift/origin-aggregated-logging/commit/61d1196eeab4ac02b360b20f9338d3ab2b5d5eef

Comment 2 Rich Megginson 2017-11-10 19:19:18 EST

koji_builds:
  https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=623852
repositories:
  brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:rhaos-3.7-rhel-7-docker-candidate-29398-20171110235311
  brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:latest
  brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:v3.7.6
  brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:v3.7.6-2
  brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-fluentd:v3.7

Comment 3 Anping Li 2017-11-14 05:00:04 EST

@Rich,
With logging-fluentd/images/v3.7.7-1. The .operations logs can be found both mux is enabled and disabled when OUPPUT label is removed. I think the test result is pass.

The bug is move from ON_QA to Modified, Is there other fix?

Comment 4 Rich Megginson 2017-11-14 09:34:54 EST

(In reply to Anping Li from comment #3)
> @Rich,
> With logging-fluentd/images/v3.7.7-1. The .operations logs can be found both
> mux is enabled and disabled when OUPPUT label is removed. I think the test
> result is pass.
> 
> The bug is move from ON_QA to Modified, Is there other fix?

Did you deploy without OPS cluster?  The bug can only be reproduced when you deploy logging without OPS cluster. If you did not deploy OPS cluster, and you could not reproduce the issue, then the bug is verified.

Comment 5 Anping Li 2017-11-14 20:54:46 EST

Yes, I had Deployed without OPS cluster.  so move to verified.

Comment 8 errata-xmlrpc 2017-12-18 08:23:56 EST

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:3464

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