-
Bug
-
Resolution: Done
-
Critical
-
Logging 6.4.0
-
Incidents & Support
-
False
-
-
False
-
NEW
-
NEW
-
Bug Fix
-
-
-
Logging - Sprint 279
-
Critical
Description of problem:
When forward logs to lokistack from inputs.syslog, the sinks.output_lokistack_receiver.endpoint is empty. The Collector pods in CrashLoopBackOff status.
Creating below CLF:
apiVersion: observability.openshift.io/v1 kind: ClusterLogForwarder metadata: name: instance-71049 namespace: openshift-logging spec: inputs: - name: syslog receiver: port: 6514 type: syslog type: receiver managementState: Managed outputs: - lokiStack: authentication: token: from: serviceAccount target: name: lokistack-71049 namespace: openshift-logging name: lokistack tls: ca: key: ca-bundle.crt secretName: lokistack-secret-71049 type: lokiStack pipelines: - inputRefs: - syslog name: forward-to-lokistack outputRefs: - lokistack serviceAccount: name: logcollector-71049
The collector pods in CrashLoopBackOff and raise below error:
$ oc logs instance-71049-2vsx7 Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/instance-71049 Starting Vector process... 2025-10-22T01:18:20.539695Z ERROR vector::cli: Configuration error. error=empty string in `sinks.output_lokistack_receiver`
In vector.toml:
[sinks.output_lokistack_receiver] type = "loki" inputs = ["output_lokistack_receiver_remap_label"] endpoint = "" out_of_order_action = "accept" healthcheck.enabled = false
Version-Release number of selected component (if applicable):
cluster-logging.v6.4.0
How reproducible:
Always
Steps to Reproduce:
See above
Actual results:
Expected results:
No error in collector pods.
Additional info:
Hit same issue when the inputs.receiver.type is http.
