** Description changed: - Dropping to di shell: + [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. - /var/log # cat syslog | grep BOOTIF - Jul 30 12:18:26 kernel: [ 0.000000] Kernel command line: nomodeset netcfg/choose_interface=auto text priority=critical auto url=http://10.228.64.209/MAAS/metadata/latest/by-id/node-b83608ea-1708-11e4-b7f0-f0921cb4cd2c/?op=get_preseed locale=en_US hostname=awaaw domain=maas log_host=10.228.64.209 log_port=514 -- earlyprintk console=ttyS0,9600n8 BOOTIF=01-fc-15-b4-17-d4-49 - Jul 30 12:18:38 netcfg[1944]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline - Jul 30 12:19:35 netcfg[1944]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline - Jul 30 12:19:37 netcfg[2050]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline - Jul 30 12:23:03 netcfg[2050]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline - /var/log # ip link - 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue - link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 - 2: bond0: <BROADCAST,MULTICAST400> mtu 1500 qdisc noqueue - link/ether 0a:09:aa:f8:b1:bf brd ff:ff:ff:ff:ff:ff - 3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq qlen 1000 - link/ether fc:15:b4:17:d4:48 brd ff:ff:ff:ff:ff:ff - 4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000 - link/ether fc:15:b4:17:d4:49 brd ff:ff:ff:ff:ff:ff + [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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350302 Title: Deploying node with di on armhf/keystone can't find BOOTIF To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1350302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
