MAAS

  1. Bug #1473167
  2. Comment #3

Comment 3 for bug 1473167

Revision history for this message
Lee Trager (ltrager) wrote :

So it looks like MAAS generates an invalid pxelinux.cfg file whenever you select a newer kernel then the base OS. If you inhibit the node from booting and grab pxelinux.cfg from MAAS by running

curl tftp://10.0.0.1/pxelinux.cfg/01-52-54-00-d9-e0-5e

You'll see

  KERNEL ubuntu/amd64/hwe-v/utopic/no-such-image/boot-kernel
  INITRD ubuntu/amd64/hwe-v/utopic/no-such-image/boot-initrd

I was able to reproduce this with hwe-u/trust, hwe-v/trusty and hwe-v-utopic. The root cause of the incorrect path is that we do not have hwe kernels for Vivid, and Utopic doesn't have a hwe kernel for Trusty.

After the node is given an invalid kernel and initrd it continues booting to disk. If the disk is blank nothing boots. I haven't figured out why the enlistment code is being rerun.

I'm going to look into patching MAAS to throw an error when the user instructs MAAS to boot something which MAAS does not have boot files for.