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.
Bug 2092361 - [NMCI] restart_L2_only_lacp test fails
Summary: [NMCI] restart_L2_only_lacp test fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-01 10:44 UTC by Vladimir Benes
Modified: 2022-11-15 12:08 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.41.3-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:50:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-123875 0 None None None 2022-06-01 10:45:38 UTC
Red Hat Product Errata RHBA-2022:8265 0 None None None 2022-11-15 10:50:16 UTC

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 10 Lubomir Rintel 2022-08-29 17:28:46 UTC 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/9d7e5a3b79c8456606deafa9ffb43db71d67a487
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
Note You need to log in before you can comment on or make changes to this bug.