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:
we fixed this for the latest releases but somehow regressed in 1.41 again. 

https://tools.dqe.lab.eng.bos.redhat.com/vbenes/nm_ci_stats/stats.html#build:;search:libnm_snapshot_reattach_unmanaged_ports_to_bridge

Version-Release number of selected component (if applicable):
1.41.2-30986.copr.a4cf48f8bc.el9

How reproducible:
?

./test_run.sh libnm_snapshot_reattach_unmanaged_ports_to_bridge

while I can run more than 20 attempts of the test with 1.41.1-30967.copr.5c3b553ea3.el9.x86_64 I am failing very soon with 1.41.1-30968.copr.0e0ac364a1.el9.x86_64

so https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/0e0ac364a1901b3e5bb56da4b37bc706555e5214 looks suspicious!

Lubo, to you!

btw I was able to fail the test after 60 attempts even with NetworkManager-1.36.0-5.el9_0.x86_64 :-(

<debug> [1663152490.8328] device[45d34e95fb71cce0] (portXa): ifindex: set ifindex 0 (old-l3cfg: c75e5c91bde4f990)
<debug> [1663152490.8328] device[3fa7cfc200be4e84] (portXc): master portXa with ifindex 0 appeared
<debug> [1663152490.8329] device[084bb6ac78acf885] (portXb): master portXa with ifindex 0 appeared

hmm, this is most certainly wrong

Marking as VERIFIED, running the scenario in a loop didn't result in a fail after 70 iterations...

version: NetworkManager-1.43.9-1.el9.x86_64

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:6585