-
Bug
-
Resolution: Done
-
Minor
-
Logging 5.8.0
Description of problem:
CLO raises below error after creating an invalid lfme CR:
E0607 07:05:14.074244 1 event.go:337] Unsupported event type: 'Error' E0607 07:05:14.080707 1 event.go:337] Unsupported event type: 'Error' E0607 07:06:14.937635 1 event.go:337] Unsupported event type: 'Error' E0607 07:06:14.942861 1 event.go:337] Unsupported event type: 'Error' E0607 07:09:20.472391 1 event.go:337] Unsupported event type: 'Error' E0607 07:09:20.478320 1 event.go:337] Unsupported event type: 'Error'
Version-Release number of selected component (if applicable):
cluster-logging.v5.8.0
How reproducible:
Always
Steps to Reproduce:
1. deploy clusterlogging with below yaml
$ cat cr.yaml apiVersion: logging.openshift.io/v1 kind: ClusterLogging metadata: namespace: openshift-logging name: instance spec: collection: type: vector logStore: elasticsearch: nodeCount: 3 redundancyPolicy: SingleRedundancy resources: requests: memory: 2Gi storage: size: 20Gi storageClassName: gp3-csi retentionPolicy: application: maxAge: 24h infra: maxAge: 3h audit: maxAge: 3h type: elasticsearch managementState: Managed visualization: kibana: replicas: 1 type: kibana
2. create lfme with below yaml:
apiVersion: logging.openshift.io/v1alpha1
kind: LogFileMetricExporter
metadata:
creationTimestamp: "2023-06-07T07:05:14Z"
generation: 1
name: test
namespace: openshift-logging
spec:
resources:
limits:
cpu: 500m
memory: 256Mi
requests:
cpu: 200m
memory: 128Mi
3. check logs in CLO
Actual results:
CLO raises error
Expected results:
CLO shouldn't raise error.
Additional info:
- links to
- mentioned on