-
Bug
-
Resolution: Unresolved
-
Critical
-
Logging 6.0.2
-
False
-
None
-
False
-
NEW
-
NEW
-
Prior to this update, configuring custom audit inputs in the ClusterLogForwarder, with a LokiStack output, caused the operator to throw errors related to nil pointer dereference. This update fixes operator code to check for nil, resolving the error.
-
Bug Fix
-
-
-
Log Collection - Sprint 262, Log Collection - Sprint 263
Description of problem:
Adding any named input of type: audit to the clf, when you have an output of type lokiStack, the CLO pod goes into crashloop upon reconcile.
Version-Release number of selected component (if applicable):
Logging 6.0, Logging 6.1
How reproducible:
Every time
Steps to Reproduce:
- Add any named input of type audit
inputs: - name: my-logs type: audit audit: sources: - openshiftAPI pipelines: - name: my-pipeline outputRefs: - my-lokistack inputRefs: - my-logs outputs: - type: lokiStack name: my-lokistack
Actual results:
CLO pod crashloop
Expected results:
Additional info:
nil exception error caused when both 'spec.infrastructure' and 'spec.receiver' are nil: https://github.com/openshift/cluster-logging-operator/blob/release-6.0/internal/api/initialize/process_pipelines.go#L100
- is cloned by
-
LOG-6468 [master] Named audit input causes nil pointer dereference exception
- MODIFIED
-
LOG-6449 [release-6.1] Named audit input causes nil pointer dereference exception
- Verified
- links to
-
RHBA-2024:143291 Logging for Red Hat OpenShift - 6.0.3
- mentioned on