[Impact]
In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting.
[Test Case]
1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description.
2. ipv6 manual, ipv4 auto
##################################
sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64;
sudo nmcli con mod bond0 ipv4.method auto;
sudo nmcli con add type bond-slave ifname ens34 master bond0;
sudo nmcli con add type bond-slave ifname ens35 master bond0;
sudo nmcli con mod bond0 +bond.options mii=100
sleep 5
sudo nmcli con up bond-slave-ens34
sudo nmcli con up bond-slave-ens35
sudo nmcli con up bond0;
sleep 5;
sudo nmcli c s bond0
##################################
3. ipv6 auto, ipv4 auto
##################################
sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
sudo nmcli con mod bond0 ipv6.method auto;
sudo nmcli con mod bond0 ipv4.method auto;
sudo nmcli con add type bond-slave ifname ens34 master bond0;
sudo nmcli con add type bond-slave ifname ens35 master bond0;
sudo nmcli con mod bond0 +bond.options mii=100
sleep 5
sudo nmcli con up bond-slave-ens34
sudo nmcli con up bond-slave-ens35
sudo nmcli con up bond0;
sleep 5
sudo nmcli c s bond0
##################################
when run #3, it is working, but with #2, it is not working.
[Potential Regression]
Actually nothing special. fix just remove if statement. but it needs Network Manager restarted.
[Other informations]
After upstream fix, it is working fine with #2 and #3 above.
* Upstream bug and fix:
https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
* Only affecting Bionic:
$ git describe --contains f03ae35
1.10.8~2
$ rmadison network-manager
==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates
network-manager | 1.20.4-2ubuntu2.2 | eoan-updates
network-manager | 1.22.4-1ubuntu2 | focal
[Original description]
---Problem Description---
Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server.
---uname output---
Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux
Machine Type = s390x
---Debugger---
A debugger is not configured
---Steps to Reproduce---
When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned.
Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface
This issue will not happen in below cases:
1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface.
2)with ipv4 automatic and ipv6 automatic configuration for bond interface
3)with ipv4 automatic and ipv6 disabled configuration for bond interface
Configuration:
Bond interface, ipv4 automatic mode and ipv6 automatic mode
root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
[connection]
id=test_bond
uuid=63e54542-5135-47ac-a954-b861c3937be2
type=bond
interface-name=test_bond
permissions=
timestamp=1537944121
[ethernet]
mac-address-blacklist=
[bond]
downdelay=0
fail_over_mac=none
miimon=100
mode=active-backup
num_grat_arp=0
primary_reselect=always
updelay=0
[ipv4]
dns-search=
method=auto
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto
From /var/log/syslog, we can see ip got assigned:
Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1
Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1
root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
28: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond
valid_lft 353sec preferred_lft 353sec
inet6 fe80::ff:feb3:b522/64 scope link
valid_lft forever preferred_lft forever
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Bond interface, ipv4 automatic mode and ipv6 manual mode
root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
[connection]
id=test_bond
uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
type=bond
interface-name=test_bond
permissions=
timestamp=1537943300
[ethernet]
mac-address-blacklist=
[bond]
downdelay=0
fail_over_mac=none
miimon=100
mode=active-backup
num_grat_arp=0
primary_reselect=always
updelay=0
[ipv4]
dns-search=
method=auto
[ipv6]
addr-gen-mode=stable-privacy
address1=fe81::32a5:bc5f:287f:8db8/64
dns-search=
method=manual
No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog
root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
29: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
valid_lft forever preferred_lft forever
==> Correct LP-Package need to be assigned...!
Which dhcp client is used? (affected package)
Notice that network-manager is not supported on Ubuntu Server 18.04,
please consider to move to netplan and networkd.
For now assuming that this is related to DHCP rather than nw mgr.