-
Bug
-
Resolution: Unresolved
-
Major
-
Logging 5.9.z
-
False
-
None
-
False
-
NEW
-
ON_QA
-
Before this update, all log sources were mounted to the collector container. With this update, only defined inputs sources are mounted.
-
Bug Fix
-
-
-
Log Collection - Sprint 261, Log Collection - Sprint 262, Log Collection - Sprint 263, Log Collection - Sprint 264, Log Collection - Sprint 265, Log Collection - Sprint 266
-
Moderate
-
Customer Escalated
Description of problem:
When using multi log forwarder and even only given the role for collecting the application logs, if entering in the collector pod, the audit, infrastructure and application logs are mounted and visible.
This is the same reported in https://issues.redhat.com/browse/LOG-4482 that was closed as Won't fix.
Version-Release number of selected component (if applicable):
RHOL 5.8 and 5.9
How reproducible:
Always
Steps to Reproduce
As described in https://issues.redhat.com/browse/LOG-4482 and detailed in the article https://access.redhat.com/solutions/7074337
Actual results:
All the type of logs are mounted, even when given only permissions through the clusterrole assigned to the service account for mounting only a type
Expected results:
It's expected to be mounted selectively the type of logs that given permissions through the clusterrolebinding assigned to the serviceAccount used.
Additional info:
- is cloned by
-
LOG-6545 [Logging 5.8] All the logs are mounted in the collector when using multi log forwarder in RHOCP 4
- Closed
- is related to
-
OBSDOCS-1128 Security warning for when setting Enabling the multi log forwarder feature for a cluster
- New
-
LOG-4482 In multiple-CLF managed collector pods, all logs are mounted to collector pods no matter what kind of logs the collector can forward.
- Closed
- links to
-
RHBA-2025:144863 Logging for Red Hat OpenShift - 5.9.11
- mentioned on