Bug 2034744 - EgressIP: assigning the same egress IP to a second EgressIP object after a ovnkube-master restart does not fail.
Summary: EgressIP: assigning the same egress IP to a second EgressIP object after a ov...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: ffernand
QA Contact: huirwang
Depends On: 2034743
Blocks: 2057152
TreeView+ depends on / blocked
Reported: 2021-12-21 21:56 UTC by Alexander Constantinescu
Modified: 2022-03-16 11:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2034743
: 2057152 (view as bug list)
Last Closed: 2022-03-16 11:38:43 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ovn-kubernetes pull 887 0 None open Bug 2034744: Fix egress IP allocator sync 2022-01-27 16:16:59 UTC
Red Hat Product Errata RHBA-2022:0798 0 None None None 2022-03-16 11:39:09 UTC

Description Alexander Constantinescu 2021-12-21 21:56:06 UTC
+++ This bug was initially created as a clone of Bug #2034743 +++

Description of problem:

There is a cache de-synchronization in ovnkube-master when restarting. All previously performed allocations are not populated in the internal cache which manages egress IP assignments, allowing for invalid assignments to be performed when ovnkube-master has restarted. 

An example of this is assigning the same egress IP to a second EgressIP object after ovnkube-master has restarted. This should not be allowed in the normal case, but is however enabled due to this problem. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create namespace "test"
3. Create an EgressIP "egressip-test" object matching namespace "test" with IP X 
4. Restart ovnkube-master (or the current leader in an HA deployment) 
5. Create a namespace "test2"
6. Create a EgressIP "egressip-test2" object matching namespace "test2" with IP X

Actual results:

IP X is assigned to "egressip-test2"

Expected results:

IP X should not be assigned to "egressip-test2" and instead trigger an event indicating: "NoMatchingNodeFound"
Additional info:

Comment 7 errata-xmlrpc 2022-03-16 11:38:43 UTC
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 (OpenShift Container Platform 4.9.24 bug fix 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.


Note You need to log in before you can comment on or make changes to this bug.