Comment 17 for bug 1736975

Revision history for this message
Lyas Spiehler (lspiehler) wrote :

I am running the latest version of Ubuntu 18.04 as a KVM hypervisor with multiple bridges. My bridges are down after reboot as described in this bug. Enabling DHCP does make the bridge come up, but I only need layer 2 on the bridges and I don't want an IP. I'm assuming assigning an IP will also work around the issue. On RHEL the config would be ONBOOT=YES. How can I make this bridge come up at boot without assigning an IP address? Here is my config:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp3s0f0:
      dhcp4: no
      dhcp6: no
    enp3s0f1:
      dhcp4: no
      dhcp6: no
    enp4s0f0:
      dhcp4: no
      dhcp6: no
    enp4s0f1:
      dhcp4: no
      dhcp6: no
  bonds:
    bond0:
      interfaces: [enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1]
      addresses: [ 10.2.10.221/24 ]
      gateway4: 10.2.10.1
      nameservers:
        search: [smhplus.org]
        addresses: [10.2.11.226, 10.2.11.227]
      parameters:
        mode: 802.3ad
        mii-monitor-interval: 1
  vlans:
    vlan1116:
      id: 1116
      link: bond0
  bridges:
    br1116:
      interfaces: [vlan1116]