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

root@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@ff:~# netplan apply
root@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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725268

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

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to