[Bug 1725268] Re: Generated config don't wait for a bond to be up

Lukas Märdian 1725268 at bugs.launchpad.net
Mon Jan 13 14:16:17 UTC 2025


I cannot seem to reproduce this issue on Focal (Netplan v0.104):

root at ff:~# netplan get
network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      dhcp4: true
  bonds:
    bond0:
      interfaces:
      - tun1
      - tun0
      parameters:
        mode: "802.3ad"
        lacp-rate: "fast"
  vlans:
    mainlan:
      addresses:
      - "192.168.111.229/24"
      id: 1
      link: "bond0"
    dmz:
      addresses:
      - "192.168.117.229/24"
      id: 3
      link: "bond0"
  tunnels:
    tun0:
      addresses:
      - "10.7.10.50/30"
      mode: "gre"
      local: "1.1.1.1"
      remote: "2.2.2.2"
    tun1:
      addresses:
      - "10.7.10.54/30"
      mode: "gre"
      local: "3.3.3.3"
      remote: "4.4.4.4"
root at ff:~# netplan apply
root at ff:~# ifconfig
bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST>  mtu 1500
        ether 4e:a8:4e:b7:cf:38  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dmz: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.117.229  netmask 255.255.255.0  broadcast 192.168.117.255
        ether 4e:a8:4e:b7:cf:38  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.238.94.77  netmask 255.255.255.0  broadcast 10.238.94.255
        inet6 fe80::216:3eff:fe67:65fb  prefixlen 64  scopeid 0x20<link>
        inet6 fd42:7213:f20e:bd74:216:3eff:fe67:65fb  prefixlen 64  scopeid 0x0<global>
        ether 00:16:3e:67:65:fb  txqueuelen 1000  (Ethernet)
        RX packets 13226  bytes 19300128 (19.3 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6006  bytes 426811 (426.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 66  bytes 7236 (7.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 66  bytes 7236 (7.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

mainlan: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.111.229  netmask 255.255.255.0  broadcast 192.168.111.255
        ether 4e:a8:4e:b7:cf:38  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

=> As can be seen "mainlan" and "dmz" have their IP address properly
assigned. This might have been fixed on the systemd-networkd side since
Bionic.

Please re-open if this is still an issue.

** No longer affects: netplan

** Changed in: netplan.io (Ubuntu)
       Status: Confirmed => Won't Fix

** Changed in: netplan.io (Ubuntu)
       Status: Won't Fix => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1725268

Title:
  Generated config don't wait for a bond to be up

Status in netplan.io package in Ubuntu:
  Invalid

Bug description:
  Try this configuration for netplan:

  network:
    version: 2
    renderer: networkd

    ethernets:
      enp2s0f0:
        dhcp4: no
      enp2s0f1:
        dhcp4: no

    bonds:
      bond0:
        parameters:
          mode: 802.3ad
          lacp-rate: fast
        interfaces:
          - enp2s0f0
          - enp2s0f1

    vlans:
      mainlan:
        id: 1
        link: bond0
        addresses: [192.168.111.229/24]
      dmz:
        id: 3
        link: bond0
        addresses: [192.168.117.229/24]

  
  ##########################################

  bond take a little time to be up, vlans are appliend immediatly and so vlans interfaces don't gets the ip.
  Using a bond different than 802.3ad there isn't this delay and vlans interfaces gets correctlr the ip.

  ifconfig result:

  bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST>  mtu 1500
          ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
          RX packets 0  bytes 0 (0.0 B)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 0  bytes 0 (0.0 B)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  dmz: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
          ether xx:xx:xx:xx:xx:xx txqueuelen 1000  (Ethernet)
          RX packets 0  bytes 0 (0.0 B)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 0  bytes 0 (0.0 B)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enp2s0f0: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
          ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
          RX packets 0  bytes 0 (0.0 B)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 0  bytes 0 (0.0 B)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
          device interrupt 222

  enp2s0f1: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
          ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
          RX packets 0  bytes 0 (0.0 B)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 0  bytes 0 (0.0 B)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
          device interrupt 225

  mainlan: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
          ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
          RX packets 0  bytes 0 (0.0 B)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 0  bytes 0 (0.0 B)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
          inet 127.0.0.1  netmask 255.0.0.0
          loop  txqueuelen 1000  (Loopback locale)
          RX packets 24  bytes 1694 (1.6 KB)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 24  bytes 1694 (1.6 KB)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  video: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
          ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
          RX packets 0  bytes 0 (0.0 B)
          RX errors 0  dropped 0  overruns 0  frame 0
          TX packets 0  bytes 0 (0.0 B)
          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 14:02:03 2017
  ProcEnviron:
   LANG=it_IT.UTF-8
   TERM=linux
   SHELL=/bin/bash
   PATH=(custom, no user)
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1725268/+subscriptions




More information about the foundations-bugs mailing list