Bug 2092361

Summary: [NMCI] restart_L2_only_lacp test fails
Product: Red Hat Enterprise Linux 9 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Lubomir Rintel <lrintel>
Status: CLOSED ERRATA QA Contact: Vladimir Benes <vbenes>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: acabral, bgalvani, lrintel, rkhan, sfaye, sukulkar, till, wenliang
Target Milestone: rcKeywords: Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.41.3-1.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 10:50:05 UTC 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-06-01 10:44:24 UTC
Description of problem:
https://tools.dqe.lab.eng.bos.redhat.com/vbenes/nm_ci_stats/stats.html#build:;search:restart_L2_only_lacp

it looks it's related to r8169 driver. Not sure how. It can easily be kernel or teamd bug. Not sure.

Version-Release number of selected component (if applicable):
kernel-5.14.0-101.el9.x86_64
NetworkManager-1.39.5-1.el9.x86_64
teamd-1.31-11.el9.x86_64

How reproducible:
always

Steps to Reproduce:
1. download NMCI test suite from https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/
2. cd NetworkManager-ci
3. ./test_run.sh restart_L2_only_lacp

Actual results:
fail

Expected results:
pass

Additional info:

Comment 1 Vladimir Benes 2022-06-01 13:20:16 UTC
simple reproducer:
[root@gsm-r5s5-01 NetworkManager-ci]# cat scrip.sh 
#!/bin/bash

nmcli con del team0 team-slave-eth5 
nmcli con down testeth0

nmcli con add type team ifname nm-team con-name team0 config '{"runner": {"name": "lacp"}, "link_watch": {"name": "ethtool"}}' ipv4.method disable ipv6.method disable 
nmcli con add type team-slave con-name team-slave-eth5 ifname eth0 master nm-team
nmcli con up team-slave-eth5

echo "restarting NM"
systemctl reset-failed NetworkManager.service
systemctl restart NetworkManager
echo "done"

nmcli con del team-slave-eth5
nmcli con up testeth0
nmcli device disconnect eth0
nmcli con up testeth0

[root@gsm-r5s5-01 NetworkManager-ci]# sh scrip.sh 
Error: unknown connection 'team0'.
Error: unknown connection 'team-slave-eth5'.
Error: cannot delete unknown connection(s): 'team0', 'team-slave-eth5'.
Connection 'testeth0' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)
Connection 'team0' (8d8fefc5-67a3-4345-828c-c154f3c0cfb8) successfully added.
Connection 'team-slave-eth5' (ba513e28-d910-435d-8eb5-3f1005a1b84a) successfully added.
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)
restarting NM
done
Connection 'team-slave-eth5' (ba513e28-d910-435d-8eb5-3f1005a1b84a) successfully deleted.
Error: Connection activation failed: No suitable device found for this connection (device eth1 not available because profile is not compatible with device (mismatching interface name)).
Error: Device 'eth0' (/org/freedesktop/NetworkManager/Devices/13) disconnecting failed: This device is not active
Error: not all devices disconnected.
Error: Connection activation failed: No suitable device found for this connection (device eth1 not available because profile is not compatible with device (mismatching interface name)).

Comment 2 Vladimir Benes 2022-06-01 13:23:10 UTC
when adding sleep 1 as below, the issue is not reproducible

echo "restarting NM"
systemctl reset-failed NetworkManager.service
systemctl restart NetworkManager
sleep 1
echo "done"

Comment 14 errata-xmlrpc 2022-11-15 10:50:05 UTC
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-2022:8265