-
Bug
-
Resolution: Done-Errata
-
Normal
-
Logging 5.8.0
-
False
-
-
False
-
NEW
-
NEW
-
Release Note Not Required
-
-
-
Log Collection - Sprint 243, Log Collection - Sprint 244, Log Collection - Sprint 245
Description of problem:
No error in CLF when the filters in filterRefs are not exist.
$ oc get clf instance -oyaml
apiVersion: logging.openshift.io/v1
kind: ClusterLogForwarder
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"logging.openshift.io/v1","kind":"ClusterLogForwarder","metadata":{"annotations":{},"name":"instance","namespace":"openshift-logging"},"spec":{"pipelines":[{"filterRefs":["my-policy","non-exist"],"inputRefs":["application","infrastructure","audit"],"name":"forward-to-default","outputRefs":["default"]}]}}
creationTimestamp: "2023-10-16T05:46:05Z"
generation: 6
name: instance
namespace: openshift-logging
resourceVersion: "192554"
uid: 7217347e-ae21-4126-919a-43bc92989633
spec:
pipelines:
- filterRefs:
- my-policy
- non-exist
inputRefs:
- application
- infrastructure
- audit
name: forward-to-default
outputRefs:
- default
status:
conditions:
- lastTransitionTime: "2023-10-16T07:14:27Z"
status: "True"
type: Ready
Version-Release number of selected component (if applicable):
openshift-logging/cluster-logging-rhel9-operator/images/v5.8.0-187
How reproducible:
Always
Steps to Reproduce:
- Create clusterlogging
- Create CLF with above yaml file
- Check status in CLF
Actual results:
No error in CLF
Expected results:
CLF should raise some validation failures.
