Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-6127

[Logging 5.8.z, Logging 5.9.z]Loki pods are in CrashLoopBackOff when the cluster has FIPS enabled.

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • Log Storage - Sprint 260
    • Critical

      Description of problem:

      Loki pods are in CrashLoopBackOff when the cluster has FIPS enabled.

       % oc get pod
      NAME                                          READY   STATUS             RESTARTS      AGE
      cluster-logging-operator-786798bfb6-hxvsr     1/1     Running            0             3m6s
      logging-loki-compactor-0                      0/1     CrashLoopBackOff   4 (25s ago)   2m29s
      logging-loki-distributor-6c96d46bf7-q6ggc     0/1     CrashLoopBackOff   4 (63s ago)   2m30s
      logging-loki-gateway-cb4f444d-kkv4b           2/2     Running            0             2m29s
      logging-loki-gateway-cb4f444d-xr8j2           2/2     Running            0             2m28s
      logging-loki-index-gateway-0                  0/1     CrashLoopBackOff   4 (42s ago)   2m29s
      logging-loki-ingester-0                       0/1     CrashLoopBackOff   4 (33s ago)   2m29s
      logging-loki-querier-54f4c4fc7c-629jl         0/1     CrashLoopBackOff   4 (60s ago)   2m29s
      logging-loki-query-frontend-f5c58698d-bjx59   0/1     CrashLoopBackOff   4 (47s ago)   2m29s
      logging-loki-ruler-0                          0/1     CrashLoopBackOff   4 (35s ago)   2m29s
      
      % oc logs logging-loki-compactor-0 
      panic: opensslcrypto: can't initialize OpenSSL : openssl: can't retrieve OpenSSL version
      
      
      goroutine 1 [running]:
      crypto/internal/backend.init.0()
      	/usr/lib/golang/src/crypto/internal/backend/openssl.go:66 +0x299 

      Version-Release number of selected component (if applicable):

      loki-operator.v5.8.13

      Cluster version: 4.14.0-0.nightly-2024-09-20-005437, 

      4.16.0-0.nightly-2024-09-19-175711

      How reproducible:

      Always

      Steps to Reproduce:

      1. deploy lokistack

      apiVersion: loki.grafana.com/v1
      kind: LokiStack
      metadata:
        name: logging-loki
        namespace: openshift-logging
      spec:
        managementState: Managed
        rules:
          enabled: true
          namespaceSelector:
            matchLabels:
              openshift.io/cluster-monitoring: "true"
          selector:
            matchLabels:
              openshift.io/cluster-monitoring: "true"
        size: 1x.demo
        storage:
          schemas:
          - effectiveDate: "2020-10-11"
            version: v11
          secret:
            name: logging-storage-secret
            type: s3
        storageClassName: gp3-csi
        tenants:
          mode: openshift-logging 

      2. check loki pods status

      Actual results:

      Expected results:

      Loki pods should be ready

      Additional info:

            ptsiraki@redhat.com Periklis Tsirakidis
            qitang@redhat.com Qiaoling Tang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: