[Bug 1350302] Re: Deploying node with di on armhf/keystone can't find BOOTIF

[Newell Jensen]

Julian,

The fix was tested with MAAS 1.5.4 as part of the certification for the
Slayton and McDivitt platforms and is no longer an issue with regards to
MAAS.  The new package is now in trusty-updates as mentioned above.

** Changed in: maas
       Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netcfg in Ubuntu.
https://bugs.launchpad.net/bugs/1350302

Title:
  Deploying node with di on armhf/keystone can't find BOOTIF

Status in MAAS:
  Fix Released
Status in “netcfg” package in Ubuntu:
  Fix Released
Status in “netcfg” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The interface=auto preseed option doesn't work on (some?) u-boot based systems, making d-i and MAAS fail in configurations where multiple external network interfaces are present.

  [Test Case]
  1) Get a u-boot-based system with multiple NICs attached.
  2) pxe boot d-i from the second NIC, passing "IPAPPEND 2" in the pxelinux config file
  3) Observe the warning "netcfg[$pid]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline" in /var/log/syslog.

  When it is working, the installer should automatically try and
  configure whatever NIC was used to pxeboot, and the above error should
  not appear in syslog.

  [Regression Risk]
  The regression risk I see is that the new BOOTIF parsing code somehow regresses this feature on non-u-boot based systems.

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