Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
connection.secondaries not updated after secondary connection removal, keeping stale UUID's there
Version-Release number of selected component (if applicable):
NetworkManager-1.42.2-1.el9.x86_64
How reproducible:
always
Steps to Reproduce:
1. have a connection with empty connection.secondaries and an e.g. VPN connection
2. Add VPN connection to base's connection.secondaries
3. delete VPN connection
Actual results:
UUID of a deleted VPN connection is still in base connection's connection.secondaries
Expected results:
UUID of deleted secondary connection is deleted from respective base connections' connection.secondaries entries
Additional info:
Already covered by NMCI scenario connection_secondaries_are_cleared_after_removal in the linked MR.
sort of similar situation is in controller/port connections, however there may be NM users depending on the current behaviour:
$ nmcli c add con-name bond0+ ifname bond0 type bond connection.autoconnect no
Connection 'bond0+' (619ef611-14f1-47e6-92cf-c580727a28dd) successfully added.
$ nmcli c add con-name bond0.10+ ifname eth10 type ethernet connection.autoconnect no master bond0+
Connection 'bond0.10+' (c6f2b280-26f1-42c3-bc50-4f475ee6a819) successfully added.
$ UUID=$(nmcli -g connection.uuid c s bond0+)
$ nmcli -f all c s bond0.10+ | grep "$UUID\|bond0+"
connection.master: 619ef611-14f1-47e6-92cf-c580727a28dd
$ nmcli c del bond0+
Connection 'bond0+' (619ef611-14f1-47e6-92cf-c580727a28dd) successfully deleted.
$ nmcli -f all c s bond0.10+ | grep "$UUID\|bond0+"
connection.master: 619ef611-14f1-47e6-92cf-c580727a28dd
$
> however there may be NM users depending on the current behaviour
Doing this as an unconditional change would clash with internal NM architecture and doing it just for secondaries would bring inconsistent behaviour. Therefore I'm self-closing this bug. In the future, I may write a feature request for an option to "nmcli c delete" which could be the same for any similar relationships and could be implemented just in NM clients (libnm, nmcli...).