-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
After configuring a AdminPolicyBasedExternalRoute with dynamic nextHop the the route is correctly added in the Gateway Router where the source pod is running, but is not taken into consideration.
-
None
-
None
-
None
-
None
Description of problem:
After configuring a AdminPolicyBasedExternalRoute with dynamic nextHop the the route is correctly added in the Gateway Router where the source pod is running, but is not taken into consideration. Also testing with ovn-trace the route used is the default.
Version-Release number of selected component (if applicable):
4.17.14
How reproducible:
always
Steps to Reproduce:
1. Create a gateway router pod
2. Create an AdminPolicyBasedExternalRoute with dynamic nextHop
3. Start egress traffic from source pods
Actual results:
Traffic using the local host to reach the external destination.
Expected results:
Traffic should be routed to the external gateway pod and reach the destination with external gateway host IP.
Additional info: