yaml file succeeds from commandline, but hangs and does not configure the interfaces on reboot

[Bill Chappell]

I am attempting to install a bridge for use with KVM or Xen and have come across a possible bug.
I am not ruling out a configuration issue, but it is successful when running from the cmdline.

This is a fresh install of Ubuntu 17.10.
Linux caballito 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

The below yaml file works from the commandline: sudo netplan apply
However, on boot, netplan appears to hang for a few minutes and NO network configuration is applied. After about 3-5min of waiting for the boot timeout and a prompt to appear, the network configuration can be applied.

## This version works from cmdline, but not on boot.
network:
 version: 2
 renderer: networkd
 ethernets:
  enp4s0:
    dhcp4: false
 bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: true

I have also tried breaking up into two files - 01-ethernets.yaml and 05-bridges.yaml, with the same results. (works from command line but not on boot)

This below file works perfectly fine - without the bridge information:
network:
  version: 2
  renderer: networkd
  ethernets:
    enp4s0:
      dhcp4: yes

[Bill Chappell (bchaps)]

OMG! Just figured it out after posting!!
I had previously installed bridge-utils for KVM and removing them appears to correct the issue.

[Mathieu Trudel-Lapierre (cyphermox)]

Do you have stuff written in /etc/network/interfaces? That might explain systemd-networkd and ifupdown fighting to set up the bridges.

Setting Incomplete so this expires if there's no response, but since you mention this is fixed by removing bridge-utils, I'm considering this "not a bug".

[Bill Chappell (bchaps)]

 Hi Mathieu!
Thanks for the response.
I want to say there was NOT anything extra in the interfaces file, but I do not remember.  There may have been.  I went through many itierations of troubleshooting.It might be worth noting somewhere that they may conflict.
This can be closed as everything is working perfectly after removing bridge-utils.
Thanks again!bill

    On Wednesday, January 10, 2018, 11:10:55 AM PST, Mathieu Trudel-Lapierre <email address hidden> wrote:

 Do you have stuff written in /etc/network/interfaces? That might explain
systemd-networkd and ifupdown fighting to set up the bridges.

Setting Incomplete so this expires if there's no response, but since you
mention this is fixed by removing bridge-utils, I'm considering this
"not a bug".

** Changed in: netplan
      Status: New => Incomplete

** Changed in: netplan
  Importance: Undecided => Low

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1739921

Title:
  yaml file succeeds from commandline, but hangs and does not configure
  the interfaces on reboot

Status in netplan:
  Incomplete

Bug description:
  I am attempting to install a bridge for use with KVM or Xen and have come across a possible bug.
  I am not ruling out a configuration issue, but it is successful when running from the cmdline.

  This is a fresh install of Ubuntu 17.10.
  Linux caballito 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  The below yaml file works from the commandline:  sudo netplan apply
  However, on boot, netplan appears to hang for a few minutes and NO network configuration is applied.  After about 3-5min of waiting for the boot timeout and a prompt to appear, the network configuration can be applied.

  ## This version works from cmdline, but not on boot.
  network:
  version: 2
  renderer: networkd
  ethernets:
    enp4s0:
      dhcp4: false
  bridges:
    br0:
      interfaces: [enp4s0]
      dhcp4: true

  I have also tried breaking up into two files - 01-ethernets.yaml and
  05-bridges.yaml, with the same results.  (works from command line but
  not on boot)

  This below file works perfectly fine - without the bridge information:
  network:
    version: 2
    renderer: networkd
    ethernets:
      enp4s0:
        dhcp4: yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1739921/+subscriptions

[Launchpad Janitor (janitor)]

[Expired for netplan because there has been no activity for 60 days.]