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.
Bug 1183424 - Need to assign a dummy IP to a bond device when enslaving to a VLAN device.
Summary: Need to assign a dummy IP to a bond device when enslaving to a VLAN device.
Keywords:
Status: CLOSED DUPLICATE of bug 1167423
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-19 02:07 UTC by Etsuji Nakai
Modified: 2015-02-20 16:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-20 16:22:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Etsuji Nakai 2015-01-19 02:07:53 UTC 
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.
Comment 2 Etsuji Nakai 2015-01-19 03:48:27 UTC 
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"
Comment 3 Lubomir Rintel 2015-02-16 19:19:26 UTC 
This was fixed in bug #1167423.

However the test case still sometimes fails due to other issues; keeping this open and investigating.
Comment 4 Lubomir Rintel 2015-02-20 16:22:28 UTC 
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 ***
Note You need to log in before you can comment on or make changes to this bug.