RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

I have tested with the patch, it seems to resolve the issue on RHEL-8.9.

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 (NetworkManager bug fix and enhancement 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-2023:7118