Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-6441

[release-6.0] Named audit input causes nil pointer dereference error

XMLWordPrintable

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

      1. 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

              cahartma@redhat.com Casey Hartman
              cahartma@redhat.com Casey Hartman
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: