Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1494310 - operations namespace logs not sent to .operations index
operations namespace logs not sent to .operations index
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.5.1
Unspecified Unspecified
urgent Severity high
: ---
: 3.5.z
Assigned To: Rich Megginson
Anping Li
:
Depends On: 1493188
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-21 21:45 EDT by Anping Li
Modified: 2017-10-25 09:08 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The pattern for container logs in the journal field CONTAINER_NAME changed. The pattern was not matching for logs from pods in the "default", "openshift", or "openshift-infra" namespaces. Consequence: Logs from these namespaces were being stored in indices matching "project.default.*" e.g. rather than ".operations.*". Fix: The pattern matcher was fixed to match the correct pattern. Result: logs from pods in the "default", "openshift", or "openshift-infra" namespaces are correctly written to the ".operations.*" indices.
Story Points: ---
Clone Of: 1493188
Environment:
Last Closed: 2017-10-25 09:08:02 EDT
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github openshift/origin-aggregated-logging/pull/668 None None None 2017-09-21 21:45 EDT
Red Hat Product Errata RHBA-2017:3049 normal SHIPPED_LIVE OpenShift Container Platform 3.6, 3.5, and 3.4 bug fix and enhancement update 2017-10-25 11:57:15 EDT

  None (edit)
Comment 1 Jeff Cantrill 2017-09-22 08:42:21 EDT
Moved to modified so it can get attached to an errata
Comment 4 errata-xmlrpc 2017-10-25 09:08:02 EDT
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.