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

[Chris J Arges]

Hello Newell, or anyone else affected,

Accepted netcfg into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/netcfg/1.116ubuntu2 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: netcfg (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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:
  Incomplete
Status in “netcfg” package in Ubuntu:
  Fix Released
Status in “netcfg” source package in Trusty:
  Fix Committed

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