Comment 13 for bug 1794478

Revision history for this message
Pedro Principeza (pprincipeza) wrote :

Hi, all. I'm afraid I'll need to reopen this bug.

I was able to reproduce the issue on Bionic, using network-manager 1.10.6-2ubuntu1.2. However, when testing this on Eoan, using network-manager 1.20.4-2ubuntu2, I didn't reproduce the behaviour.

The steps one takes to reproduce the issue, either on a s390 system or x86 (the issue is reproducible regardless of the platform) is:

1.) Create the bond interface with:
nmcli conn add type bond con-name <name> ifname <device> ipv4.method disabled ipv6.method ignore

2.) Modify it to so set a manual IPv6 Address and auto-assign IPv4:
nmcli c m <uuid> bond.options " mode=active-backup, downdelay=0 , miimon=100 , updelay=0 , fail_over_mac=none , num_grat_arp=0 , primary_reselect=always " connection.interface-name <device name> ipv4.method auto ipv4.gateway "" ipv6.method manual 802-3-ethernet.mac-address "" ipv4.routes "" connection.id <connection name> ipv6.never-default no ipv4.addresses "" ipv6.addresses <provide manual ipv6>

3.) Add the two slave ethernet devices, and change them with:

nmcli c m <uuid> connection.id <ethernet device id> connection.interface-name <ethernet connection name> 802-3-ethernet.s390-subchannels <device subchannels> 802-3-ethernet.s390-nettype qeth connection.autoconnect yes 802-3-ethernet.mac-address "" ipv4.method disabled ipv6.method ignore 802-3-ethernet.s390-options portno=<valid portno>

^ For repro steps on amd64 or ppc64, the s390-* parameters can be removed from the command.

4.) Add the two slave ethernet devices to the bond:

nmcli c m <slave uuid> 802-3-ethernet.mac-address "" connection.master <master uuid> connection.slave-type bond

[ . . . ]

You'll see that, on Bionic, the bond interface isn't assigned an IPv4 address. On Eoan, an IPv4 address is assigned as expected.

I have reviewed network-manager's changelog [1], but I didn't find any smoking guns that could've solved the issue, hence the re-opening of the bug.

Let me know if further evidence is needed to proceed. Thanks!

[1] https://changelogs.ubuntu.com/changelogs/pool/main/n/network-manager/network-manager_1.20.4-2ubuntu2/changelog