-
Bug
-
Resolution: Done
-
Major
-
Logging 5.9.0
-
False
-
None
-
False
-
NEW
-
NEW
-
Release Note Not Required
-
-
-
Log Collection - Sprint 250, Log Collection - Sprint 251
-
Moderate
Description of problem:
CLO keeps reporting below errors after creating a CLF:
{"_ts":"2024-03-13T08:15:19.880990517Z","_level":"0","_component":"cluster-logging-operator","_message":"clusterlogforwarder-controller returning, error","_error":{"msg":"error removing stale http input services"}} {"_ts":"2024-03-13T08:15:19.891834129Z","_level":"0","_component":"cluster-logging-operator","_message":"Warning: Reconciler returned both a non-zero result and a non-nil error. The result will always be ignored if the error is non-nil and the non-nil error causes reqeueuing with exponential backoff. For more details, see: https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/reconcile#Reconciler","ClusterLogForwarder":{"name":"instance","namespace":"openshift-logging"},"controller":"clusterlogforwarder","controllerGroup":"logging.openshift.io","controllerKind":"ClusterLogForwarder","name":"instance","namespace":"openshift-logging","reconcileID":"069a8911-fd6c-42d1-9e52-0298256033f1"} {"_ts":"2024-03-13T08:15:19.892047619Z","_level":"0","_component":"cluster-logging-operator","_message":"Reconciler error","ClusterLogForwarder":{"name":"instance","namespace":"openshift-logging"},"_error":{"msg":"error removing stale http input services"},"controller":"clusterlogforwarder","controllerGroup":"logging.openshift.io","controllerKind":"ClusterLogForwarder","name":"instance","namespace":"openshift-logging","reconcileID":"069a8911-fd6c-42d1-9e52-0298256033f1"}
CLF:
apiVersion: logging.openshift.io/v1 kind: ClusterLogForwarder metadata: name: instance namespace: openshift-logging spec: pipelines: - detectMultilineErrors: false inputRefs: - infrastructure - audit - application name: forward-to-default outputRefs: - default
Version-Release number of selected component (if applicable):
cluster-logging-rhel9-operator/images/v5.9.0-81
How reproducible:
Always
Steps to Reproduce:
- Deploy logging
- Create CLF to forward logs to default log store
- Check logs in CLO pod
Actual results:
CLO keeps reporting errors.
Expected results:
No error in CLO.