-
Bug
-
Resolution: Won't Do
-
Undefined
-
None
-
4.14.z
-
Moderate
-
Yes
-
False
-
-
Description of problem:
BMER hw-event-proxy container will not start and shows error, "version `GLIBC_2.32' not found"
$ oc get pods -n openshift-bare-metal-events NAME READY STATUS RESTARTS AGE hw-event-proxy-85b4df5d75-dnxbj 2/3 CrashLoopBackOff 12 (3m15s ago) 39m
$ oc logs -n openshift-bare-metal-events hw-event-proxy-85b4df5d75-dnxbj hw-event-proxy /hw-event-proxy: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /hw-event-proxy)
Version-Release number of selected component (if applicable):
bare-metal-event-relay.v4.14.5-27
How reproducible:
100%
Steps to Reproduce:
1. Deploy 4.14 SNO with openshift-bare-metal-events operator
2. Check status of openshift-bare-metal-events pods
3. Check hw-event-proxy logs
Actual results:
$ oc get pods -n openshift-bare-metal-events NAME READY STATUS RESTARTS AGE hw-event-proxy-85b4df5d75-dnxbj 2/3 CrashLoopBackOff 12 (3m15s ago) 39m $ oc logs -n openshift-bare-metal-events hw-event-proxy-85b4df5d75-dnxbj hw-event-proxy /hw-event-proxy: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /hw-event-proxy)
Expected results:
operator starts successfully and logs events
Additional info:
Cluster version is 4.14.27