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.
Created attachment 1715649[details]
Reproduce script
Description of problem:
The bond0 has VLAN bond0.20.
When deactivating bond0 profile, and activate it again, the VLAN profile is not
automatically reactivated.
Version-Release number of selected component (if applicable):
NetworkManager-1.26.0-7.el8.x86_64
nmstate-0.3.4-12.el8
How reproducible:
100%
Steps to Reproduce:
1. sudo bash ./nm_bug.sh
2.
3.
Actual results:
The `ip link` show no `bond0.20` interface.
Expected results:
The `ip link` show no `bond0.20` interface.
Additional info:
Run `nmstatectl set net.json` twice is the key reproducer.
Change it to run it one time does not trigger this problem.
So I think there is some race problem here.
(In reply to Gris Ge from comment #1)
> Created attachment 1715650[details]
> System logs with NM trace enabled
we see:
<trace> [1600760863.0641] settings-connection[7d9a2ee357f05c84,a38470de-f0a4-42ca-afac-0b21af6f2d64]: autoconnect: blocked reason: user-request
...
<info> [1600760863.0648] audit: op="connection-update" uuid="a38470de-f0a4-42ca-afac-0b21af6f2d64" name="bond0.20" args="ipv4.dhcp-client-id,ipv6.addr-gen-mode,ipv6.dhcp-duid,ipv6.dhcp-iaid,connection.lldp" pid=1412 uid=0 result="success"
and afterwards there is on D-Bus command to unblock the autoactivation (or explicit activation of the profile, which would automatically unblock autoconnect).
To me it seems NetworkManager is behaving as expected.
Created attachment 1715649 [details] Reproduce script Description of problem: The bond0 has VLAN bond0.20. When deactivating bond0 profile, and activate it again, the VLAN profile is not automatically reactivated. Version-Release number of selected component (if applicable): NetworkManager-1.26.0-7.el8.x86_64 nmstate-0.3.4-12.el8 How reproducible: 100% Steps to Reproduce: 1. sudo bash ./nm_bug.sh 2. 3. Actual results: The `ip link` show no `bond0.20` interface. Expected results: The `ip link` show no `bond0.20` interface. Additional info: Run `nmstatectl set net.json` twice is the key reproducer. Change it to run it one time does not trigger this problem. So I think there is some race problem here.