-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.13.z, 4.14.z, 4.15.0
-
None
-
Critical
-
Yes
-
False
-
Description of problem:
when setting up cluster with FIPS enabled. and setup sriov operator, network-resources-injector crashed with error # oc logs network-resources-injector-rcl2j -n openshift-sriov-network-operator FIPS mode is enabled, but this binary is not compiled with FIPS compliant mode enabled # oc get pod -n openshift-sriov-network-operator NAME READY STATUS RESTARTS AGE network-resources-injector-88m26 0/1 CrashLoopBackOff 49 (4m14s ago) 3h49m network-resources-injector-ddflw 0/1 CrashLoopBackOff 49 (3m43s ago) 3h49m network-resources-injector-rcl2j 0/1 CrashLoopBackOff 49 (4m4s ago) 3h49m operator-webhook-mrk7x 1/1 Running 0 3h49m operator-webhook-t9fg2 1/1 Running 0 3h49m operator-webhook-xbhtc 1/1 Running 0 3h49m sriov-device-plugin-96zfl 1/1 Running 0 2m20s sriov-device-plugin-xnnqt 1/1 Running 0 2m18s sriov-network-config-daemon-2v9xw 1/1 Running 1 3h49m sriov-network-config-daemon-58wbt 1/1 Running 0 3h49m sriov-network-config-daemon-bbjqx 1/1 Running 2 3h49m sriov-network-config-daemon-ch9rf 1/1 Running 0 3h49m sriov-network-config-daemon-nf88k 1/1 Running 0 3h49m sriov-network-operator-69cbbfd847-78r94 1/1 Running 0 3h49m
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- depends on
-
OCPBUGS-22704 network-resources-injector pods crashed on FIPS cluster
- Closed
- is depended on by
-
OCPBUGS-22365 [4.13.z]network-resources-injector pods crashed on FIPS cluster
- Closed
- links to
-
RHBA-2023:6836 OpenShift Container Platform 4.14.z bug fix update