-
Bug
-
Resolution: Done
-
Critical
-
Logging 5.6.24
-
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 pods NAME READY STATUS RESTARTS AGE cluster-logging-operator-df84b4bcf-tqxcr 1/1 Running 0 54m lokistack-sample-compactor-0 0/1 CrashLoopBackOff 7 (95s ago) 13m lokistack-sample-distributor-7597797f68-tznhz 0/1 CrashLoopBackOff 7 (117s ago) 13m lokistack-sample-gateway-854d87d7d7-779lz 2/2 Running 0 13m lokistack-sample-gateway-854d87d7d7-8xrgw 2/2 Running 0 13m lokistack-sample-index-gateway-0 0/1 CrashLoopBackOff 7 (2m9s ago) 13m lokistack-sample-ingester-0 0/1 CrashLoopBackOff 7 (106s ago) 13m lokistack-sample-querier-768d77d494-6whm9 0/1 CrashLoopBackOff 7 (116s ago) 13m lokistack-sample-query-frontend-59cdcbcdd6-xvz8x 0/1 CrashLoopBackOff 7 (2m20s ago) 13m lokistack-sample-ruler-0 0/1 CrashLoopBackOff 7 (118s ago) 13m oc logs lokistack-sample-compactor-0panic: 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:50 +0x244
Version-Release number of selected component (if applicable):
loki-operator.v5.6.24
Cluster version: 4.13.0-0.nightly-arm64-2024-09-26-214441
How reproducible:
Always
Steps to Reproduce:
1. deploy lokistack
oc get lokistack lokistack-sample -o yaml |yq '.spec' managementState: Managed rules: enabled: true namespaceSelector: matchLabels: openshift.io/cluster-monitoring: "true" selector: matchLabels: openshift.io/cluster-monitoring: "true" size: 1x.extra-small storage: schemas: - effectiveDate: "2020-10-11" version: v11 secret: name: s3-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:
- links to
-
RHBA-2024:138714 Logging for Red Hat OpenShift - 5.8.13
- mentioned on