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 2130287 - ports can be left attached when controller dependency fails early
Summary: ports can be left attached when controller dependency fails early
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Matej Berezny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-27 17:46 UTC by Thomas Haller
Modified: 2023-05-09 10:22 UTC (History)
7 users (show)

Fixed In Version: NetworkManager-1.41.3-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 08:17:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
logfile showing the issue (2.36 MB, text/plain)
2022-09-27 17:46 UTC, Thomas Haller 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-266 0 None None None 2023-02-08 08:43:24 UTC
Red Hat Issue Tracker RHELPLAN-135073 0 None None None 2022-09-27 17:48:46 UTC
Red Hat Product Errata RHBA-2023:2485 0 None None None 2023-05-09 08:17:52 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1246 0 None opened bond: added bond_unattach_ports_on_controller_failure test 2022-11-21 09:59:19 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1406 0 None opened device: fix hanging port devices when controller goes down while port is not fully attached 2022-09-29 13:05:27 UTC

Description Thomas Haller 2022-09-27 17:46:54 UTC 
Created attachment 1914638 [details]
logfile showing the issue

See attached logfile.


that was th/mlag-bonding-slb branch (on top of current `main`, 3871c670ab9417fc54d3c0450e91e08ced4a98b4).


First, we create a bond profile + 5 port profiles. Then, the bond gets activated with autoconnect-slaves on. During "ip-config" state something happens and, and 

            _LOGD(LOGD_BOND, "balance-slb: failed");
            nm_device_state_changed(NM_DEVICE(self),
                                    NM_DEVICE_STATE_FAILED,
                                    NM_DEVICE_STATE_REASON_CONFIG_FAILED);

gets called:

<info>  [1664299540.9661] device (bond0): state change: secondaries -> failed (reason 'config-failed', sys-iface-state: 'managed')

The first time, we are already in state "secondaries". Consequently we see 

<trace> [1664299540.9667] device[6b76ac7314eb0b53] (bond0): master: release one slave a9f10ea824bb1725/eth1 (enslaved) (configure)

and all the port profiles get correctly deactivated.


Later, try the same again. This time:

<info>  [1664299566.1065] device (bond0): state change: ip-config -> failed (reason 'config-failed', sys-iface-state: 'managed')
...
<trace> [1664299566.1073] device[6b76ac7314eb0b53] (bond0): master: release one slave a9f10ea824bb1725/eth1 (not enslaved) (configure)


the result is that the devices linger indefinitely in ip-config state and don't get wrapped up, although the controller is gone.
Comment 1 Thomas Haller 2022-09-28 19:17:54 UTC 
patch on review at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1385
Comment 2 Thomas Haller 2022-09-29 13:05:28 UTC 
(In reply to Thomas Haller from comment #1)
> patch on review at
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/
> merge_requests/1385

No proposed fix on MR https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1406

Seems this was a regression introduced in 1.40 by commit 1fe8166fc9fb93dc64992325e31e7611725aaeb2.
Comment 3 Thomas Haller 2022-10-07 08:59:39 UTC 
fixed by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1406
Comment 7 errata-xmlrpc 2023-05-09 08:17:33 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-2023:2485
Note You need to log in before you can comment on or make changes to this bug.