Description of problem: Can not assign multiple EgressIPs to a namespace by using automatic way. Version-Release number of selected component (if applicable): 4.8.0-0.ci-2021-04-12-230600 How reproducible: Always Steps to Reproduce: 1. Patch EgressCIDRs to 2 nodes. oc get hostsubnet NAME HOST HOST IP SUBNET EGRESS CIDRS EGRESS IPS huirwang-48-7whjx-master-0 huirwang-48-7whjx-master-0 172.31.249.27 10.129.0.0/23 huirwang-48-7whjx-master-1 huirwang-48-7whjx-master-1 172.31.249.16 10.128.0.0/23 huirwang-48-7whjx-master-2 huirwang-48-7whjx-master-2 172.31.249.107 10.130.0.0/23 huirwang-48-7whjx-worker-kslk9 huirwang-48-7whjx-worker-kslk9 172.31.249.167 10.129.2.0/23 huirwang-48-7whjx-worker-mt9rh huirwang-48-7whjx-worker-mt9rh 172.31.249.149 10.131.0.0/23 ["172.31.249.0/24"] [] huirwang-48-7whjx-worker-t7htk huirwang-48-7whjx-worker-t7htk 172.31.249.209 10.128.2.0/23 ["172.31.249.0/24"] [] 2. Create a namespace test, patch multiple EgressIPs to "test". oc get netnamespace test NAME NETID EGRESS IPS test 1502728 ["172.31.249.201","172.31.249.202"] 3. Check hostsubnet and nodes which were assigned EgressCIDRs Actual results: No EgressIPs assigned to the nodes which were holding EgressCIDRs. oc get hostsubnet NAME HOST HOST IP SUBNET EGRESS CIDRS EGRESS IPS huirwang-48-7whjx-master-0 huirwang-48-7whjx-master-0 172.31.249.27 10.129.0.0/23 huirwang-48-7whjx-master-1 huirwang-48-7whjx-master-1 172.31.249.16 10.128.0.0/23 huirwang-48-7whjx-master-2 huirwang-48-7whjx-master-2 172.31.249.107 10.130.0.0/23 huirwang-48-7whjx-worker-kslk9 huirwang-48-7whjx-worker-kslk9 172.31.249.167 10.129.2.0/23 huirwang-48-7whjx-worker-mt9rh huirwang-48-7whjx-worker-mt9rh 172.31.249.149 10.131.0.0/23 ["172.31.249.0/24"] [] huirwang-48-7whjx-worker-t7htk huirwang-48-7whjx-worker-t7htk 172.31.249.209 10.128.2.0/23 ["172.31.249.0/24"] [] [core@huirwang-48-7whjx-worker-t7htk ~]$ ip a show ens192 2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:ac:26:7b brd ff:ff:ff:ff:ff:ff inet 172.31.249.209/23 brd 172.31.249.255 scope global dynamic noprefixroute ens192 valid_lft 6214sec preferred_lft 6214sec inet6 fe80::eb6f:c940:e64e:304a/64 scope link noprefixroute valid_lft forever preferred_lft foreve [core@huirwang-48-7whjx-worker-mt9rh ~]$ ip a show ens192 2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:ac:9f:b1 brd ff:ff:ff:ff:ff:ff inet 172.31.249.149/23 brd 172.31.249.255 scope global dynamic noprefixroute ens192 valid_lft 6230sec preferred_lft 6230sec inet6 fe80::d57:e2e7:ef40:873a/64 scope link noprefixroute valid_lft forever preferred_lft forever Expected results: Can assign multiple EgressIPs by automatic assignments. Additional info:
Setting the blocker flag to + as the new feature "load balancing for egress IP" will not be feature complete without it. I will submit a patch soon.
*** Bug 1949607 has been marked as a duplicate of this bug. ***
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438