Bug 1881318
| Summary: | VLAN of bond does not automatically activated after bond profile reactivated | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Gris Ge <fge> | ||||||
| Component: | NetworkManager | Assignee: | Thomas Haller <thaller> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Vladimir Benes <vbenes> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 8.4 | CC: | acardace, atragler, bgalvani, bsanford, lrintel, rkhan, sukulkar, till, vbenes | ||||||
| Target Milestone: | rc | Keywords: | Reopened, Triaged | ||||||
| Target Release: | 8.4 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | NetworkManager-1.30.0-0.7.el8 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1923958 (view as bug list) | Environment: | |||||||
| Last Closed: | 2021-02-02 10:01:49 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1738136, 1923958 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1715650 [details]
System logs with NM trace enabled
Issue has been fixed by NetworkManager-tui-1.30.0-0.7.el8.x86_64.rpm I(Gris) will do the root cause investigation. I reopen the issue to understand why it is/seems fixed now. We should still understand the original problem before closing. Closing as it is fixed, we can investigate how it's been fixed after the dev freeze for RHEL 8.4 as we simply do not have the capacity now. (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.