Bug 1183424
| Summary: | Need to assign a dummy IP to a bond device when enslaving to a VLAN device. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Etsuji Nakai <enakai> |
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lrintel> |
| Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | CC: | danw, dcbw, jklimes, lrintel, thaller |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-20 16:22:28 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: | |||
This is the same for a team device. I need to assign a dummy loopback IP to team0 as below. # nmcli c add type team ifname team0 con-name team-team0 # nmcli c mod team-team0 ipv4.method manual ipv4.addresses "127.0.0.2/8" # nmcli c add type team-slave ifname ens6 con-name team-slave-ens6 master team-team0 # nmcli c add type team-slave ifname ens7 con-name team-slave-ens7 master team-team0 # nmcli c add type vlan ifname vlan10 con-name vlan-vlan10 dev team0 id 10 # nmcli c mod vlan-vlan10 ipv4.method manual ipv4.addresses "192.168.10.11/24" This was fixed in bug #1167423. However the test case still sometimes fails due to other issues; keeping this open and investigating. I've filed an upstream review requests for the issues I've encountered: https://bugzilla.gnome.org/show_bug.cgi?id=744812 Closing this as a duplicate. Please re-check with 7.1 version of NetworkManager. If you encounter any other issues that you'd like to see fixed please open separate tickets. Thank you! *** This bug has been marked as a duplicate of bug 1167423 *** |
Description of problem: I tried to add a bond device bond0 to a VLAN device vlan10. In this config, I don't need to assign an IP to bond0, but it doesn't work without an IP on bond0. Version-Release number of selected component (if applicable): # cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.0 (Maipo) # rpm -qa | grep NetworkManager NetworkManager-glib-0.9.9.1-29.git20140326.4dba720.el7_0.x86_64 NetworkManager-0.9.9.1-29.git20140326.4dba720.el7_0.x86_64 NetworkManager-config-server-0.9.9.1-29.git20140326.4dba720.el7_0.x86_64 NetworkManager-tui-0.9.9.1-29.git20140326.4dba720.el7_0.x86_64 # uname -a Linux rhel7 3.10.0-123.13.2.el7.x86_64 #1 SMP Fri Dec 12 19:51:03 EST 2014 x86_64 x86_64 x86_64 GNU/Linux Steps to Reproduce: 1. Intended configuration ens6 -| |--bond0--vlan10 (192.168.10.11/24) ens7 -| 2. Create a bonding device bond0 without IP. # nmcli c add type bond ifname bond0 con-name bond-bond0 mode active-backup # nmcli c mod bond-bond0 ipv4.method disable # nmcli c add type bond-slave ifname ens6 con-name bond-slave-ens6 master bond0 # nmcli c add type bond-slave ifname ens7 con-name bond-slave-ens7 master bond0 3. Enslave bond0 to a VLAN device vlan10. # nmcli c add type vlan ifname vlan10 con-name vlan-vlan10 dev bond0 id 10 # nmcli c mod vlan-vlan10 ipv4.method manual ipv4.addresses "192.168.10.11/24 192.168.10.1" 4. Activate connections. # nmcli c down bond-slave-ens6 # nmcli c down bond-slave-ens7 # nmcli c down bond-bond0 # nmcli c down vlan-vlan10 # nmcli c up bond-slave-ens6 # nmcli c up bond-slave-ens7 # nmcli c up bond-bond0 Error: Timeout 90 sec expired. # nmcli c up vlan-vlan10 As above, activation of bond-bond0 fails as it tries to get IP address via DHCP even though ipv4.method is disabled. # nmcli d DEVICE TYPE STATE CONNECTION ens6 ethernet connected bond-slave-ens6 ens7 ethernet connected bond-slave-ens7 eth0 ethernet connected eth0 bond0 bond connecting (getting IP configuration) bond-bond0 lo loopback unmanaged -- # nmcli -f ipv4.method c show bond-bond0 ipv4.method: disabled Expected results: bonding device should be configured not to assign an IP according to ipv4.method = disabled.