Bug 1304641
| Summary: | bond profile doubling after restart with manual ipv6 (or ignore) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> | ||||
| Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.3 | CC: | aloughla, bgalvani, lrintel, rkhan, thaller | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 7.3 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | NetworkManager-1.2.0-1.el7 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-11-03 19:07:20 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: | |||||||
| Attachments: |
|
||||||
|
Description
Vladimir Benes
2016-02-04 09:16:26 UTC
this scenario is incorrect too: [root@wlan-r2s26 ~]# nmcli connection add type bond con-name bond0 ip4 1.1.1.2/24 ip6 1::2/128 Connection 'bond0' (49cb4fbb-7bf2-4e7f-a455-f85546b31e45) successfully added. [root@wlan-r2s26 ~]# nmcli con show -a NAME UUID TYPE DEVICE testeth0 8e4cdf82-a18a-4881-bb08-7cef1a499132 802-3-ethernet eth0 bond0 49cb4fbb-7bf2-4e7f-a455-f85546b31e45 bond nm-bond [root@wlan-r2s26 ~]# systemctl restart NetworkManager [root@wlan-r2s26 ~]# nmcli con show -a NAME UUID TYPE DEVICE testeth0 8e4cdf82-a18a-4881-bb08-7cef1a499132 802-3-ethernet eth0 nm-bond 2433457b-6cb8-44bf-9e27-a42bd297cd01 bond nm-bond [root@wlan-r2s26 ~]# nmcli connection up id bond0 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) [root@wlan-r2s26 ~]# nmcli con show -a NAME UUID TYPE DEVICE bond0 49cb4fbb-7bf2-4e7f-a455-f85546b31e45 bond nm-bond testeth0 8e4cdf82-a18a-4881-bb08-7cef1a499132 802-3-ethernet eth0 [root@wlan-r2s26 ~]# systemctl restart NetworkManager [root@wlan-r2s26 ~]# nmcli con show -a NAME UUID TYPE DEVICE testeth0 8e4cdf82-a18a-4881-bb08-7cef1a499132 802-3-ethernet eth0 nm-bond 1a1bb393-ce17-4574-b7b9-e302792312b8 bond nm-bond [root@wlan-r2s26 ~]# nmcli connection up id bond0 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) [root@wlan-r2s26 ~]# nmcli connection down id bond0 Connection 'bond0' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) [root@wlan-r2s26 ~]# nmcli d DEVICE TYPE STATE CONNECTION eth0 ethernet connected testeth0 nm-bond bond disconnected -- ^^ the bond shouldn't be here, right? and whatmore: [root@wlan-r2s26 ~]# nmcli connection up id bond0 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3) [root@wlan-r2s26 ~]# nmcli connection delete bond0 Connection 'bond0' (49cb4fbb-7bf2-4e7f-a455-f85546b31e45) successfully deleted. [root@wlan-r2s26 ~]# nmcli d DEVICE TYPE STATE CONNECTION eth0 ethernet connected testeth0 nm-bond bond disconnected -- ^^ this creates stalled bond device Created attachment 1121106 [details]
journal log
This should be fixed by the patches posted in bug 1299103, which add new bonding options and improve the connection matching logic for bonds (since the two things are related it makes sense to keep those changes together). This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions test case written and bug verified as gone 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, 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://rhn.redhat.com/errata/RHSA-2016-2581.html |