Bug 2221903

Summary: [AWS]Adding an eni to an EC2 instance sometimes breaks network because ip rules/tables get ruined
Product: Red Hat Enterprise Linux 8 Reporter: libhe
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: VERIFIED --- QA Contact: Filip Pokryvka <fpokryvk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.9CC: bgalvani, desktop-qa-list, linl, lrintel, rkhan, sfaye, sukulkar, till, wenliang, xiliang, ymao
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-1.40.16-9.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Bug Depends On: 2207812    
Bug Blocks:    

Description libhe 2023-07-11 08:34:39 UTC
Description of problem:

This is a same bug with 2207812, it is also observed in RHEL-8.9.  

Sometimes when adding a 3rd interface to an EC2 instance, the 2nd interface ends up using the same rule and route table as the new interface.

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

How reproducible:
Frequently by building new RHEL8.9 instance.  Once issue is reproduced, instance becomes inaccessible, then detaching the interface and rebooting returns instance to ready-to-be-reproduced state, then adding the same 3rd interface frequently reproduces the problem again.

Steps to Reproduce:
1.Launch a r5a.24xlarge instance using ami-0a558068fc4385358 (us-west-2) from  RHEL-8.9.0 image.

2. Once it's running, attach a secondary ENI to the instance.

3. Try and attach another ENI to the instance.

Actual results:
instance hangs when 2nd instance ip rule/route table conflict occurs.

Expected results:
ip rules/route tables do not conflict.

Additional info:

Comment 3 libhe 2023-07-18 14:13:15 UTC
I have tested with the patch, it seems to resolve the issue on RHEL-8.9.