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

From RHOL 5.7.0 clf.spec.pipelines.name field is not optional

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • Logging 5.7.0
    • Log Collection
    • False
    • Hide

      None

      Show
      None
    • False
    • NEW
    • NEW
    • Hide

      1) Check "oc explain" output about the field "clf.spec.pipelines.name"

      $ oc explain clf.spec.pipelines.name
KIND:     ClusterLogForwarder
VERSION:  logging.openshift.io/v1

FIELD:    name <string>

DESCRIPTION:
     Name is optional, but must be unique in the `pipelines` list if provided.

      2) Install RHOL 5.7.0 ( using Vector)

      3) Create a CLF without a "clf.spec.pipelines.name"

      spec:
  pipelines:
  - inputRefs:
    - application
    outputRefs:
    - default

      4) Check the CLF instance status:

      status:
  conditions:
  - lastTransitionTime: "2023-05-16T13:51:29Z"
    message: No valid inputs, outputs, or pipelines. Invalid CLF spec.
    reason: Invalid
    status: "False"
    type: Ready
  outputs:
    default:
    - lastTransitionTime: "2023-05-16T13:51:29Z"
      status: "True"
      type: Ready
  pipelines:
    pipeline_0_:
    - lastTransitionTime: "2023-05-16T13:51:29Z"
      message: pipeline must have a name
      reason: Invalid
      status: "False"
      type: Ready

      As a workaround, adding a name to the pipeline, the issue is solved.

      Testing in RHOL 5.6.5 with the same CLF instance we are not able to see the same problem:

      spec:
  pipelines:
  - inputRefs:
    - application
    outputRefs:
    - default
status:
  conditions:
  - lastTransitionTime: "2023-05-16T14:14:31Z"
    status: "True"
    type: Ready
  inputs:
    audit:
    - lastTransitionTime: "2023-05-16T14:14:31Z"
      status: "True"
      type: Ready
    infrastructure:
    - lastTransitionTime: "2023-05-16T14:14:31Z"
      status: "True"
      type: Ready
  outputs:
    default:
    - lastTransitionTime: "2023-05-16T14:14:31Z"
      status: "True"
      type: Ready
  pipelines:
    pipeline_0_:
    - lastTransitionTime: "2023-05-16T14:14:31Z"
      status: "True"
      type: Ready
      Show
      1) Check "oc explain" output about the field "clf.spec.pipelines.name" $ oc explain clf.spec.pipelines.name KIND: ClusterLogForwarder VERSION: logging.openshift.io/v1 FIELD: name <string> DESCRIPTION: Name is optional, but must be unique in the `pipelines` list if provided. 2) Install RHOL 5.7.0 ( using Vector) 3) Create a CLF without a "clf.spec.pipelines.name" spec: pipelines: - inputRefs: - application outputRefs: - default 4) Check the CLF instance status: status: conditions: - lastTransitionTime: "2023-05-16T13:51:29Z" message: No valid inputs, outputs, or pipelines. Invalid CLF spec. reason: Invalid status: "False" type: Ready outputs: default : - lastTransitionTime: "2023-05-16T13:51:29Z" status: "True" type: Ready pipelines: pipeline_0_: - lastTransitionTime: "2023-05-16T13:51:29Z" message: pipeline must have a name reason: Invalid status: "False" type: Ready As a workaround, adding a name to the pipeline, the issue is solved. Testing in RHOL 5.6.5 with the same CLF instance we are not able to see the same problem: spec: pipelines: - inputRefs: - application outputRefs: - default status: conditions: - lastTransitionTime: "2023-05-16T14:14:31Z" status: "True" type: Ready inputs: audit: - lastTransitionTime: "2023-05-16T14:14:31Z" status: "True" type: Ready infrastructure: - lastTransitionTime: "2023-05-16T14:14:31Z" status: "True" type: Ready outputs: default : - lastTransitionTime: "2023-05-16T14:14:31Z" status: "True" type: Ready pipelines: pipeline_0_: - lastTransitionTime: "2023-05-16T14:14:31Z" status: "True" type: Ready
    • Log Collection - Sprint 236

      Description of problem:

      After installing/updating RHOL to 5.7.0, the field "clf.spec.pipelines.name" is not optional

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

      RHOL 5.7.0

      Expected results:

      According to "oc explain clf.spec.pipelines.name" and previous RHOL versions, the field "clf.spec.pipelines.name" should be optional.

              jcantril@redhat.com Jeffrey Cantrill
              acandelp Adrian Candel
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: