Collector pods can't forward logs to Splunk due to weak CA certificate key in RHOCP 4

Solution Verified - Updated -

Issue

  • Collector pods can't send logs to Splunk when CA certificate key is weak.
  • Collector pods stream below logs:

    2023-03-30T18:57:05.749071Z ERROR vector::internal_events::http_client: HTTP error. error=error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1915:: CA certificate key too weak error_type="request_failed" stage="processing"
    2023-03-30T18:57:05.749150Z ERROR vector::topology::builder: msg="Healthcheck: Failed Reason." error=Failed to make HTTP(S) request: error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1915:: CA certificate key too weak component_kind="sink" component_type="splunk_hec" component_id=splunk_receiver component_name=splunk_receiver
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.10+
  • Red Hat OpenShift Logging (RHOL)
    • 5.6+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content