kernel boot command line for baremetal assumes block device UUID is correct root

[Robert Collins]

It does this by checking blkid on the device it wrote the image too, but if the image contains lvm or any other translation layer, this won't be the actual UUID to use.

We may be better off with a LABEL that we can document every image to have (e.g. cloudimg-rootfs)

this can be worked around for now by editing the template

root=${ROOT} -> root=LABEL=cloudimg-rootfs

[Joe Gordon (jogo)]

Since we are in the process of deprecating nova maremetal, we should focus work on ironic instead.

[Dmitry Tantsur (divius)]

Note for implementer: this will likely require a written spec

[John Stafford (john-stafford)]

Devananda - I noticed that Dmitry indicated on this bug that it will likely require a spec.. Are we good with keeping this as a bug or should we push it to L?

[Lucas Alvares Gomes (lucasagomes)]

I've put up a spec (which is now merged) that allows you to PXE boot an image using a specific kernel command line for that image. See: https://review.openstack.org/#/c/177859/

With that you can boot from a different root filesystem.

The code is here (waiting for reviews): https://review.openstack.org/#/c/178229/

[Lucas Alvares Gomes (lucasagomes)]

The bug is being closed because the fix is now being proposed as a spec