-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14
-
+
-
Important
-
No
-
Rejected
-
False
-
-
Previous to this change, EgressIP hosted by an interface that is not the primary interface did not consider if a next hop is required. With this change, it will now inspect the main routing table and determine if a next hop is required.
-
Enhancement
-
In Progress
-
-
-
-
-
Description of problem:
When we test the Egress on secondary-nic, we faced the connectivity issue due to missing the default route from secondary-nic.
Version-Release number of selected component (if applicable):
OCP 4.14.1
How reproducible:
Steps to Reproduce:
1. Install NMState operator 2. Create NMState CR and NNCE with secondary-nic 3. Create Egressip CR on worker-X(Gateway node) 4. Create a test pod on worker-Y
Actual results:
Failed to reach the external httpd-server on secondary-nic
Expected results:
Test the pod by curl to your httpd-server and check access_log to see if Egressip selected as intended
Additional info:
Details of the issue and troubleshooting with Tim Rozet on slack is here https://redhat-internal.slack.com/archives/CDCP2LA9L/p1698942743094839
- links to
-
RHBA-2024:2051 OpenShift Container Platform 4.14.z bug fix update