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:

When using `nmcli d reapply <iface_name>` for changes to `connection.mptcp-flags`, NetworkManager generate no error message but MPTCP flags haven't changed.

Version-Release number of selected component (if applicable):
NetworkManager-1.41.0-30856.copr.711f69fb73.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. nmcli c eth1 ens3 connection.mptcp-flags signal
2. nmcli d reapply eth1
3. npc mptcp

Actual results:

MPTCP flags not changed, no error generated.

Expected results:

Neither support reapplying mptcp or raise an error.

Additional info:

I cannot reproduce this.

Can you please attach a complete level=TRACE log?


Note that as usually, reapply takes a while before all changes take effect. That is, during reapply we might restart DHCP, which takes time, but `nmcli device reapply` already returned before all that is completed. That may or may not be a bug...

Created attachment 1910007 [details]
NetworkManager trace log

I have waited 30 seconds after `nmcli d reapply`, the mptcp flags is not changed.

VERIFIED in NetworkManager-1.41.6-1.el9: I can see NM using MPTCP for a connection after manual setting of connection.mptcp-flags to non-null.

Automated test will follow as a part of MPTCP tests.

Tested at NM level by NMCI scenarios ipv4_mptcp_reapply_change_flag, ipv4_mptcp_remove_endpoints.

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