Verified this bug on oc v3.11.128 with steps 1. Create cluster on 3.11 with networkpolicy plugin 2. Create new project 3. Added egressip for namespaces. eg: oc patch netnamespace z1 -p '{"egressIPs":["10.0.76.100"]}' 4. Added egressip on one node, eg: oc patch hostsubnet preserve-zzhao-311nrr-1 -p '{"egressIPs":["10.0.76.100"]}' 5. Create test pod to make sure it scheduled to node (not the egress ip node) 6. rsh into the test pod and ping one blocked ip 7. check the sdn logs of node which same the test pod and there isn't any logs show node is offline.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1753