-
Bug
-
Resolution: Done
-
Blocker
-
Logging 5.8.0
-
False
-
-
False
-
NEW
-
VERIFIED
-
Release Note Not Required
-
-
-
Log Collection - Sprint 241, Log Collection - Sprint 242
Description of problem:
Vector pods can't forward logs to default lokistack and raise many warning messages:
2023-08-24T09:12:03.809884Z WARN sink{component_kind="sink" component_id=default_loki_apps component_type=loki component_name=default_loki_apps}: vector::internal_events::http_client: HTTP error. error=error trying to connect: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1889:: self-signed certificate in certificate chain error_type="request_failed" stage="processing" internal_log_rate_limit=true
2023-08-24T09:12:03.809959Z WARN sink{component_kind="sink" component_id=default_loki_apps component_type=loki component_name=default_loki_apps}: vector::sinks::util::retries: Retrying after error. error=Failed to make HTTP(S) request: Failed to make HTTP(S) request: error trying to connect: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1889:: self-signed certificate in certificate chain internal_log_rate_limit=true
Version-Release number of selected component (if applicable):
openshift-logging/cluster-logging-rhel9-operator/images/v5.8.0-123
How reproducible:
Always
Steps to Reproduce:
- Deploy lokistack
- Create CL with:
apiVersion: logging.openshift.io/v1 kind: ClusterLogging metadata: name: instance namespace: openshift-logging spec: collection: type: vector logStore: lokistack: name: loki-53817 type: lokistack managementState: Managed visualization: type: ocp-console
Actual results:
Get `No datapoints found` when checking data in lokistack.
Expected results:
Logs should be sent to lokistack without error.
Additional info:
- links to
- mentioned on
