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

Bug #1725268 reported by ZioTibia81
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
netplan
New
Undecided
Unassigned
netplan.io (Ubuntu)
Confirmed
Undecided
Unassigned

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)

Revision history for this message
ZioTibia81 (ziotibia81) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plan (Ubuntu):
status: New → Confirmed
Thomas (t.c)
affects: plan (Ubuntu) → netplan.io (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.