-
Bug
-
Resolution: Done
-
Major
-
Logging 5.5.6, Logging 5.6.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
Before this update, creating a `ClusterLogForwarder` custom resource (CR) with an output value of `default` did not generate any errors. With this update, an error warning this value is invalid generates appropriately.
-
-
-
Log Collection - Sprint 229, Log Collection - Sprint 230, Log Collection - Sprint 231, 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:
- deploy CLO
- create a CLF, add an output named `default`
- 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