Code review comment for lp://staging/~andreserl/maas-images/maas_images_signed_kernel

Thanks for pointing that out Steve. lp:maas-images looks for a file in /boot starting with the name vmlinuz[1]. Since the unsigned vmlinuz filename is shorter then the signed filename I suspect lp:maas-images will end up using the unsigned kernel. That will need to be fixed in order for MAAS to use a signed kernel in the ephemeral environment.

lp:maas-images will only generate a new image if a new image is posted upstream [2]. That being said is there any reason not to fix this for releases no longer supported?

[1] http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/meph2/netinst.py#L327
[2] http://cloud-images.ubuntu.com/daily/