Bug 2125615

Summary:	[NMCI] libnm_snapshot_reattach_unmanaged_ports_to_bridge regressed
Product:	Red Hat Enterprise Linux 9	Reporter:	Vladimir Benes <vbenes>
Component:	NetworkManager	Assignee:	Fernando F. Mancera <ferferna>
Status:	VERIFIED ---	QA Contact:	David Jaša <djasa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	bgalvani, ferferna, lrintel, rkhan, sfaye, sukulkar, till, wenliang
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.43.90-1.el9	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:

Description Vladimir Benes 2022-09-09 13:08:16 UTC

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

Comment 2 Vladimir Benes 2022-09-14 14:28:32 UTC

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!

Comment 3 Vladimir Benes 2022-09-14 14:29:23 UTC

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

Comment 4 Lubomir Rintel 2022-09-30 14:24:22 UTC

<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

Comment 8 David Jaša 2023-08-10 13:25:03 UTC

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