Bug 2105801 - [Azure] IP address creation: After deleting and recreating egressIP object, egress traffic was intermittently broke for about 1 minute
Summary: [Azure] IP address creation: After deleting and recreating egressIP object...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.12.z
Assignee: Patryk Diak
QA Contact: huirwang
URL:
Whiteboard:
Depends On: 2101992
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-10 16:52 UTC by Andreas Karis
Modified: 2023-02-02 11:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2101992
Environment:
Last Closed: 2023-02-02 11:09:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 jechen 2022-09-22 14:57:02 UTC 
Mark this as TestBlocker, as currently automated cases can not be run on Azure due to this bug, and there is no regression test coverage on Azure for egressIP
Comment 7 Andreas Karis 2022-10-11 14:23:29 UTC 
Just to reiterate: this clearly looks like an issue in the Azure layer as this can easily be reproduced by just spawning 2 VMs, assigning a static secondary IP to the first VM from inside linux, and then attaching an ipconfig with that static IP to the first VM from Azure; one can observe significant delay between the success manage from Azure and traffic actually passing when one runs a continuous ping sourced from the secondary IP of VM1 to VM2.
Comment 8 Andreas Karis 2022-10-17 13:34:30 UTC 
I am taking the TestBlocker off of this bug. It's clearly a problem with the cloud platform and not on our end. I'll have to get back to this, but for the time being I'd suggest adding a sleep or something to the tests between the configuration and the validation step.
Note You need to log in before you can comment on or make changes to this bug.