Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-665

flowlogs-pipeline is stuck at ContainerCreating and is never ready

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Console Plugin, FLP, Loki, Operator
    • None
    • False
    • None
    • False
    • NetObserv - Sprint 227, NetObserv - Sprint 228
    • Important

      flowlogs-pipeline is stuck at ContainerCreating status when you configure it to enable TLS and have it skip validating the server certificate for Loki. This configuration is necessary when you use Loki Operator because it uses https and has a self-signed certificate. In the Flow Collector UI, set enable: True and insecureSkipVerify: True in the tls > loki section.

      There is no notification that something went wrong. In Observe > Network Traffic, there is no data and also no errors. However, if you go to Workloads > Pods and select Project: netobserv, the status of flowlogs-pipeline-* is ContainerCreating (see attachment). There are no logs for flowlogs-pipeline-*.

      Workaround:
      After further investigation, there is a simple workaround. The problem is that in the tls > loki > caCert section, it is defaulting to values for a certificate that doesn't exist. The "name" attribute is "loki" and the "certFile" is "service-ca.crt". Minimally, clear the attribute for "name" and it will now work! Optionally, it should clear the "certFile" field as well.

            ocazade@redhat.com Olivier Cazade
            stlee@redhat.com Steven Lee
            Amogh Rameshappa Devapura Amogh Rameshappa Devapura
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: