-
Bug
-
Resolution: Done
-
Major
-
None
-
ACM 2.9.0
-
None
-
Submariner Sprint 2023-11
-
Critical
-
No
Description of problem:
ACM 2.9 / Submariner 0.16.0
OpenShift 4.14 OVN-IC on AWS platform
During deployment of ACM 2.9 with Submariner 0.16.0 on aws platform with ocp 4.14 OVN-IC, the submariner gateway node was created but stays in the "NodeReady" state.
The ocp 4.13 cluster on aws was able to successfully deploy gateway node and bring it to the ready state.
NAME STATUS ROLES AGE VERSION ip-10-0-16-112.us-east-2.compute.internal Ready worker 123m v1.27.4+2c83a9f ip-10-0-164-238.us-east-2.compute.internal NotReady infra,worker 26m v1.27.4+2c83a9f ip-10-0-2-119.us-east-2.compute.internal Ready control-plane,master 131m v1.27.4+2c83a9f ip-10-0-33-109.us-east-2.compute.internal Ready worker 122m v1.27.4+2c83a9f ip-10-0-40-90.us-east-2.compute.internal Ready control-plane,master 131m v1.27.4+2c83a9f ip-10-0-66-39.us-east-2.compute.internal Ready control-plane,master 131m v1.27.4+2c83a9f ip-10-0-76-167.us-east-2.compute.internal Ready worker 123m v1.27.4+2c83a9f
NAME DESIRED CURRENT READY AVAILABLE AGE mbabushk-aws-xvmv8-submariner-gw-us-east-2b 1 1 29m mbabushk-aws-xvmv8-worker-us-east-2a 1 1 1 1 133m mbabushk-aws-xvmv8-worker-us-east-2b 1 1 1 1 133m mbabushk-aws-xvmv8-worker-us-east-2c 1 1 1 1 133m
machine-controller.log, machineset-controller.log and addons from spoke and hub clusters log files attached.
