Customer reported auto egress IP problems. Examination of logs and code reveals problems with (1) changing the EgressIP of a NetNamespace while its existing EgressIP is active, and (2) assigning duplicate EgressIPs to the same NetNamespaces or the same HostSubnets. Nodes will not always successfully recover from these situations (without being restarted) due to messed-up internal state
Tested with 3.10.0-0.47.0
The egressIP works fine with the conditions in comment#0.
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.