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

[master] No error in the clf instance when creating a clf with an output named as `default`.

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Hide
      Before this update, creating a `ClusterLogForwarder` custom resource (CR) with an output named `default` did not generate an error as expected. The output validation has now been corrected. With this update, an error warning that the name is reserved, shows as expected.
      Show
      Before this update, creating a `ClusterLogForwarder` custom resource (CR) with an output named `default` did not generate an error as expected. The output validation has now been corrected. With this update, an error warning that the name is reserved, shows as expected.
    • Log Collection - Sprint 232

      Description of problem:

      When create clf/instance with below file, there is no error in clf:

      $ oc get clf -oyaml
      apiVersion: v1
      items:
      - apiVersion: logging.openshift.io/v1
        kind: ClusterLogForwarder
        metadata:
          creationTimestamp: "2022-12-16T08:43:10Z"
          generation: 1
          name: instance
          namespace: openshift-logging
          resourceVersion: "262832"
          uid: 6887a972-bfda-454f-ae32-d83a5689b805
        spec:
          outputs:
          - name: default
            secret:
              name: loki-client
            type: loki
            url: https://logs-prod-us-central1.grafana.net
          pipelines:
          - inputRefs:
            - application
            name: to-loki
            outputRefs:
            - default
        status:
          conditions:
          - lastTransitionTime: "2022-12-16T08:43:10Z"
            status: "True"
            type: Ready
      kind: List
      metadata:
        resourceVersion: ""

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

      cluster-logging.v5.6.0

      How reproducible:

      Always

      Steps to Reproduce:

      1. deploy CLO
      2. create a CLF, add an output named `default`
      3. check CLF status

      Actual results:

      No error in CLF.

      Expected results:

      Should have error message like:

            - lastTransitionTime: "2020-07-07T01:43:04Z"
              message: output name "default" is reserved
              reason: Invalid
              status: "False"
              type: Ready

      Additional info:

              cahartma@redhat.com Casey Hartman
              qitang@redhat.com Qiaoling Tang
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: