MaaS on older releases need support for newer curtin images

[Stefan Bader]

This came up when we chatted about problems using Xenial images on Maas this morning. And it will likely become a big problem when Xenial is released. Server environments do not change that quickly, so we should expect hosts running Trusty (cloud-archive or maas from the PPA) trying to provision Xenial.

This currently is broken because the smarts of the curtin installer seems to have changed and the rootfs-tgz (the base filesystem used) no longer comes with the kernel (and modules) pre-installed. But the init phase of older curtin versions does not include steps to download a kernel from the archive. So we end up with a client that starts the final reboot without any kernel installed.

[Scott Moser (smoser)]

Note that curtin at sufficient level is currently available in
 * xenial
 * ppa:maas/next-proposed https://launchpad.net/~maas/+archive/ubuntu/next-proposed
 * ppa:maas/proposed https://launchpad.net/~maas/+archive/ubuntu/proposed

[Scott Moser (smoser)]

fixed in curtin trunk in revision 324.
http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/revision/324

[Scott Moser (smoser)]

I've marked affecting maas as this needs transitioning from proposed ppas to next or stable.

[Andres Rodriguez (andreserl)]

Hi Scott,

Could you please also start the SRU process. 1.9.0 has SRU in process.

[Scott Moser (smoser)]

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.