Bug 1936802 - (release-4.7) Authentication log gatherer shouldn't scan all the pod logs in the openshift-authentication namespace
Summary: (release-4.7) Authentication log gatherer shouldn't scan all the pod logs in ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Insights Operator
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.z
Assignee: Tomas Remes
QA Contact: Pavel Šimovec
Depends On: 1936798
TreeView+ depends on / blocked
Reported: 2021-03-09 08:20 UTC by Tomas Remes
Modified: 2021-04-05 13:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1936798
Last Closed: 2021-04-05 13:56:14 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift insights-operator pull 369 0 None open [release-4.7] Bug 1936802: Authentication log gatherer - do not scan … 2021-03-10 08:44:14 UTC
Red Hat Product Errata RHSA-2021:1005 0 None None None 2021-04-05 13:56:32 UTC

Description Tomas Remes 2021-03-09 08:20:00 UTC
+++ This bug was initially created as a clone of Bug #1936798 +++

Description of problem:
Authentication log gatherer scans all the pod logs in the openshift-authentication namespace, but it searches only one specific error message (at the moment) related to the OAuth. 

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

How reproducible:

Steps to Reproduce:

Actual results:
Scanning all the pod logs in the openshift-authentication namespace.

Expected results:
Scan only oauth-openshift pod logs. 

Additional info:

--- Additional comment from Tomas Remes on 2021-03-09 08:18:11 UTC ---

Should be fixed with https://github.com/openshift/insights-operator/pull/365.

Comment 4 errata-xmlrpc 2021-04-05 13:56:14 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 (Moderate: OpenShift Container Platform 4.7.5 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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