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

Bad output status formating

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • NEW
    • Hide
      Before to this update, the CLF would indicate validation errors in the status, but the outputs and pipeline status did not accurately reflect the specific issues. With this update, we have revamped the status format for pipelines to accurately display Validation Fail reasons in case of misconfigured outputs, inputs, or filters. This enhancement ensures that the pipeline status now correctly reflects issues related to validation failures.
      Show
      Before to this update, the CLF would indicate validation errors in the status, but the outputs and pipeline status did not accurately reflect the specific issues. With this update, we have revamped the status format for pipelines to accurately display Validation Fail reasons in case of misconfigured outputs, inputs, or filters. This enhancement ensures that the pipeline status now correctly reflects issues related to validation failures.
    • Bug Fix
    • Log Collection - Sprint 245

    Description

      Description of problem:

      The CLF displays validation errors in the status but the outputs and pipeline status is not correct for the individual issues

      apiVersion: logging.openshift.io/v1
kind: ClusterLogForwarder
metadata:
  creationTimestamp: "2023-11-15T19:05:06Z"
  generation: 1
  name: instance
  namespace: openshift-logging
  resourceVersion: "53862"
  uid: 1d8f65af-360c-4464-8972-92e4586122ca
spec:
  outputs:
  - limit:
      maxRecordsPerSecond: 100
    name: default
    type: loki
  pipelines:
  - inputRefs:
    - application
    outputRefs:
    - default
status:
  conditions:
  - lastTransitionTime: "2023-11-15T19:05:06Z"
    reason: ValidationFailure
    status: "False"
    type: Ready
  - lastTransitionTime: "2023-11-15T19:05:06Z"
    message: clusterlogforwarder is not ready
    reason: ValidationFailure
    status: "True"
    type: Validation
  outputs:
    output_0_:
    - lastTransitionTime: "2023-11-15T19:05:06Z"
      message: output name "default" is reserved
      reason: Invalid
      status: "False"
      type: Ready
  pipelines:
    pipeline_0:
    - lastTransitionTime: "2023-11-15T19:05:06Z"
      message: 'invalid: unrecognized outputs: [default], no valid outputs'
      reason: Invalid
      status: "False"
      type: Ready

      The output or pipeline should reflects something like:

          pipeline_0:
    - lastTransitionTime: "2023-11-15T19:05:06Z"
      message: 'invalid: unrecognized outputs: [default], no valid outputs'
      reason: ValidationFailure
      status: "True"
      type: Validation

      where 'status: "True"' means the condition applies

      Attachments

        Activity

          People

            vparfono Vitalii Parfonov
            jcantril@redhat.com Jeffrey Cantrill
            Anping Li Anping Li
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: