Comment 7 for bug 1350302

Julian,

I will verify this for you within the next day or two.

Newell

On Mon, Sep 1, 2014 at 7:35 PM, Julian Edwards <email address hidden>
wrote:

> Can someone please tell me if this bug is still an issue after the
> netcfg fix?
>
> ** Changed in: maas
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>
> Bug description:
> Dropping to di shell:
>
> /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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1350302/+subscriptions
>