netcfg fails to recognize BOOTIF

Bug #1363681 reported by Jens Elkner on 2014-08-31
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
netcfg (Ubuntu)
Undecided
Unassigned

Bug Description

I'm trying to create a hands-off server installation, however, it seems impossible wrt. Ubuntu. One thing is the buggy netcfg:

Aug 31 15:29:26 netcfg[696]: INFO: Starting netcfg v.1.116ubuntu1 (built 20140403-1424)
...
Aug 31 15:29:26 netcfg[696]: INFO: Could not find valid BOOTIF= entry in /proc/cmdline

But: cat /proc/cmdline
BOOT_IMAGE=http://141.44.24.61/boot/ubuntu-14.04.1-server-amd64/vmlinuz ks=http://pkg/cgi-bin/ubuntu priority=low ksdevice=bootif BOOT_DEBUG=3 nousbnet textonly console=ttyS1,115200 initrd=http://141.44.24.61/boot/ubuntu-14.04.1-server-amd64/initrd.gz BOOTIF=01-00-25-90-eb-9e-aa

Jens Elkner (jelmd) wrote :

Digging around I found the curent runk for netconfig and saw, that it probably finds BOOTIF= now and used this binary instead. However, it doesn't seem to work (at least not as I expect it, i.e. what other distros/demos do). So I created the follwoing patches, which make it work.

Jens Elkner (jelmd) wrote :
Jens Elkner (jelmd) wrote :

The attachment "patch 1" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Jens Elkner (jelmd) wrote :

BTW: the netcfg of the current netboot image (xenial) coredumps very often, is absolutely unreliable now. Shuold be replaced by udhcpc.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers