kernel-packages team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

heres the diagnosis of the failure here:

a.) the powerVM system was successfully booting and installing xenial,
but was failing to bring up networking on the installed system.

b.) curtin had written (as designed) /etc/udev/rules.d/70-persistent-net.rules containing a line like:
  SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:f2:e9:5d:be:68", NAME="eth0"

c.) curtin had written an /etc/network/interfaces file like:
   auto eth0
   iface eth0 inet dhcp

d.) the cert team had curtin configuration (late_commands) that was writing /etc/network/interfaces in the target with "dhcp on everything".  In order to do this, they read the device names from the install environment via /sys/class/net/ .  This resulted in /etc/network/interfaces like:
  auto enP2p1s0f0
  iface enP2p1s0f0 inet dhcp


When the system booted, networking failed to come up because there was no device named 'enP2p1s0f0', as 70-persistent rules named it 'eth0'.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1563055

Title:
  IBM ppc64le MAAS images booting with no network

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The latest daily Xenial image for MAAS seems to lack network
  connectivity. Tested with kernel version 4.4.0-15 from the 20160328
  image from the daily stream

  Attached are logs from the boot sequence as well as the maas
  deployment logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+subscriptions