Bug 2106444

Summary:	EgressnodeIP update need special logic to handle creation errors
Product:	OpenShift Container Platform	Reporter:	Mohamed Mahmoud <mmahmoud>
Component:	Networking	Assignee:	Mohamed Mahmoud <mmahmoud>
Networking sub component:	ovn-kubernetes	QA Contact:	jechen <jechen>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	surya
Version:	4.11
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-17 19:52:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mohamed Mahmoud 2022-07-12 17:11:18 UTC

Description of problem:
Egress nodeIP update path need to call addNodeForEgress() to recover creation failures followed immediatly by an update before retryobjs get a chance to retry failed creation.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 jechen 2022-08-19 22:38:22 UTC

Verified in 4.12.0-0.nightly-2022-08-19-072813

Ran all egressIP automated cases on both AWS and GCP with OVN-Kubernetes plugin


 The Case Execution Summary:
 PASS OCP-47017 Author:huirwang Multiple projects use same EgressIP. [Serial] 
 PASS OCP-47018 Author:huirwang Multiple projects use same EgressIP. [Serial] 
 PASS OCP-47019 Author:huirwang EgressIP works well with networkpolicy and egressFirewall. [Serial] 
 PASS OCP-47020 Author:huirwang EgressIP node liveness probe. [Disruptive] [Serial]
 PASS OCP-47021 Author:huirwang lr-policy-list and snat should be updated correctly after remove pods. [Disruptive] [Serial]
 PASS OCP-47023 Author:huirwang EgressIP works well with networkpolicy and egressFirewall. [Serial] 
 PASS OCP-47024 Author:huirwang EgressIP node liveness probe. [Disruptive] [Serial]
 PASS OCP-47025 Author:huirwang Be able to update egressip object. [Serial] 
 PASS OCP-47026 Author:huirwang Deleting EgressIP object and recreating it works. [Serial] 
 PASS OCP-47028 Author:huirwang After remove EgressIP node tag, EgressIP will failover to other availabel egress nodes. [Serial] 
 PASS OCP-47030 Author:huirwang An EgressIP object can not have multiple egress IP assignments on the same node. [Serial] 
 PASS OCP-47031 Author:huirwang After reboot egress node EgressIP still work. [Disruptive] [Serial]
 PASS OCP-47032 Author:huirwang Traffic is load balanced between egress nodes. [Serial] 
 PASS OCP-47033 Author:huirwang If an egress node is NotReady traffic is still load balanced between available egress nodes. [Disruptive] [Serial]
 PASS OCP-47034 Author:huirwang Traffic is load balanced between egress nodes. [Serial] 
 PASS OCP-47163 Author:huirwang Deleting EgressIP object and recreating it works. [Serial] 
 PASS OCP-47164 Author:huirwang Be able to update egressip object. [Serial] 
 PASS OCP-47208 Author:huirwang The configured EgressIPs exceeds IP capacity. [Disruptive] [Serial]
 PASS OCP-47272 Author:huirwang Pods will not be affected by the egressIP set on other netnamespace. [Serial] 
 PASS OCP-53069 Author:huirwang [Bug2097243] EgressIP should work for recreated same name pod. [Serial]

Comment 5 errata-xmlrpc 2023-01-17 19:52:29 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 (Moderate: OpenShift Container Platform 4.12.0 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-2022:7399