-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.14
-
None
-
Critical
-
No
-
False
-
Description of problem:
Ingress node firewall tests failing on ARM64 platform
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-arm64-2023-07-05-041509
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
Operator installation is blocked due to controller-manager crash [anusaxen@anusaxen verification-tests]$ oc get all -n openshift-ingress-node-firewall NAME READY STATUS RESTARTS AGE pod/ingress-node-firewall-controller-manager-7b8b4bdb84-w82vg 1/2 CrashLoopBackOff 2 (21s ago) 41sNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/ingress-node-firewall-controller-manager-metrics ClusterIP None <none> 9300/TCP 45s service/ingress-node-firewall-controller-manager-service ClusterIP 172.30.146.189 <none> 443/TCP 42s service/ingress-node-firewall-daemon-metrics ClusterIP None <none> 9301/TCP 46s service/ingress-node-firewall-webhook-service ClusterIP 172.30.13.48 <none> 443/TCP 44sNAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/ingress-node-firewall-controller-manager 0/1 1 0 41sNAME DESIRED CURRENT READY AGE replicaset.apps/ingress-node-firewall-controller-manager-7b8b4bdb84 1 1 0 41s [anusaxen@anusaxen verification-tests]$ oc logs pod/ingress-node-firewall-controller-manager-7b8b4bdb84-w82vg -n openshift-ingress-node-firewall exec /manager: exec format error
Expected results:
Operator installation shouldn't be blocked
Additional info: