Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2034744

Summary: EgressIP: assigning the same egress IP to a second EgressIP object after a ovnkube-master restart does not fail.
Product: OpenShift Container Platform Reporter: Alexander Constantinescu <aconstan>
Component: NetworkingAssignee: ffernand <ffernand>
Networking sub component: ovn-kubernetes QA Contact: huirwang
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: anusaxen, ffernand, trozet
Version: 4.7   
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2034743
: 2057152 (view as bug list) Environment:
Last Closed: 2022-03-16 11:38:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2034743    
Bug Blocks: 2057152    

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.

https://access.redhat.com/errata/RHBA-2022:0798