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

Vector logs show configuration error when an output pipeline is not used in the CLF instance

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • Hide
      Before this change moving to vector deployments from fluentd would cause the pod not to start when an output was spec'd in ClusterLogForwarder but not referenced by any pipeline. This change fixes that by dropping the output during reconciliation and adding a status condition to ClusterLogForwarder
      Show
      Before this change moving to vector deployments from fluentd would cause the pod not to start when an output was spec'd in ClusterLogForwarder but not referenced by any pipeline. This change fixes that by dropping the output during reconciliation and adding a status condition to ClusterLogForwarder
    • Bug Fix
    • Proposed
    • Medium
    • Hide

      1) Deploy RHOL 5.7.4 version with Vector as collector.

      2) Deploy a CLF with an output that is not used for sending the logs:

      spec:
        outputs:
        - name: forwarder -->this output is not used for storing the logs
          syslog:
            facility: local0
            rfc: RFC5424
          type: syslog
          url: udp://test:224
        pipelines:
        - inputRefs:
          - application
          name: forwarder2
          outputRefs:
          - default
      

      3) Check Vector logs:

      2023-08-04T07:50:33.358443Z ERROR vector::cli: Configuration error. error=Transform "forwarder_json" has no inputs
       

      4) Collector pods are in CrashLoopBackOff/Error status

       

      collector-52qmm                                 1/2     CrashLoopBackOff   2 (26s ago)   46s
      collector-88wzk                                 1/2     Error              3 (31s ago)   47s
      collector-mn9gs                                 1/2     Error              3 (31s ago)   47s
      collector-sfrp8                                 1/2     Error              3 (28s ago)   50s
      collector-tcncr                                 1/2     CrashLoopBackOff   2 (27s ago)   46s
      collector-znz9g                                 1/2     CrashLoopBackOff   2 (28s ago)   47s
      

       

       

      The workaround is to delete the output pipeline that is not used for the CLF instance.

      Show
      1) Deploy RHOL 5.7.4 version with Vector as collector. 2) Deploy a CLF with an output that is not used for sending the logs: spec:   outputs:   - name: forwarder --> this output is not used for storing the logs     syslog:       facility: local0       rfc: RFC5424     type: syslog     url: udp: //test:224   pipelines:   - inputRefs:     - application     name: forwarder2     outputRefs:     - default 3) Check Vector logs: 2023-08-04T07:50:33.358443Z ERROR vector::cli: Configuration error. error=Transform "forwarder_json" has no inputs   4) Collector pods are in CrashLoopBackOff/Error status   collector-52qmm                                 1/2     CrashLoopBackOff   2 (26s ago)   46s collector-88wzk                                 1/2     Error              3 (31s ago)   47s collector-mn9gs                                 1/2     Error              3 (31s ago)   47s collector-sfrp8                                 1/2     Error              3 (28s ago)   50s collector-tcncr                                 1/2     CrashLoopBackOff   2 (27s ago)   46s collector-znz9g                                 1/2     CrashLoopBackOff   2 (28s ago)   47s     The workaround is to delete the output pipeline that is not used for the CLF instance.
    • Log Collection - Sprint 242, Log Collection - Sprint 243
    • Moderate

      Description of problem:

      When deployed a CLF instance with an output pipeline that is not used, the Vector logs show us the following configuration issue log:

      2023-08-04T07:50:33.358443Z ERROR vector::cli: Configuration error. error=Transform "$pipeline_json" has no inputs

       

       

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

      cluster-logging.v5.7.4

      Actual results:

      Error in Vector logs when an output pipeline is not used

      Expected results:

      No errors in Vector logs when an output pipeline is not used 

      Additional info:

      This is happening in this Vector version, I tested with previous versions and I don't find any errors. In addition, I also change the collector to Fluentd and no issues.

            jcantril@redhat.com Jeffrey Cantrill
            acandelp Adrian Candel
            Anping Li Anping Li
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: