fails to bring up network bridge

Bug #1432173 reported by Philip Muškovac
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Probably a dup of #1430675

After upgrading to vivid with systemd my network bridge isn't configured on boot:

$ systemctl --all |grep ifup
● ifup-wait-all-auto.service loaded failed failed Wait for all "auto" /etc/network/interfaces to be up for network-online.target
● <email address hidden> loaded failed failed ifup for eth0
  <email address hidden> loaded active exited ifup for eth1
  <email address hidden> loaded active exited ifup for lxcbr0
  <email address hidden> loaded active exited ifup for virbr0/nic
  <email address hidden> loaded active exited ifup for virbr0
  <email address hidden> loaded active exited ifup for wlan0
  system-ifup.slice loaded active active system-ifup.slice

$ journalctl -u ifup-wait-all-auto.service
-- Logs begin at Sat 2015-03-14 15:17:08 CET, end at Sat 2015-03-14 15:21:30 CET. --
Mar 14 15:17:56 yofel-desktop systemd[1]: Starting Wait for all "auto" /etc/network/interfaces to be up for network-online.target...
Mar 14 15:17:56 yofel-desktop sh[1114]: Segmentation fault
Mar 14 15:19:56 yofel-desktop systemd[1]: ifup-wait-all-auto.service start operation timed out. Terminating.
Mar 14 15:19:56 yofel-desktop systemd[1]: Failed to start Wait for all "auto" /etc/network/interfaces to be up for network-online.target.
Mar 14 15:19:56 yofel-desktop systemd[1]: Unit ifup-wait-all-auto.service entered failed state.
Mar 14 15:19:56 yofel-desktop systemd[1]: ifup-wait-all-auto.service failed.

$ sudo ifconfig br0 up
br0: ERROR while getting interface flags: No such device

$ sudo ifup br0
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
Waiting for DAD... Done

resolv.conf is intentionally a regular file. But after running "ifup" the bridge works fine.

interfaces:
auto lo br0
iface lo inet loopback

iface eth0 inet manual

iface br0 inet static
address 192.168.1.5
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth1
bridge_stp off
bridge_maxwait 0
bridge_fd 0

iface br0 inet6 static
address fec0::218:f3ff:fe2c:eb60/64
netmask 64

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Sat Mar 14 15:29:24 2015
InstallationDate: Installed on 2011-01-03 (1530 days ago)
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=9c833d6f-4685-4a19-ad27-fa60a77a4054 ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1238
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Philip Muškovac (yofel) wrote :
tags: added: systemd-boot
description: updated
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Martin, I'm afraid to not be knowledgeable enough in the network changes you have made. Mind having a look once your are back?

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

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

Changed in systemd (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
importance: Undecided → High
Revision history for this message
Martin Pitt (pitti) wrote :

Treating it as a duplicate for now.

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.