zfsonroot vm ends up with aws kernel

[Andreas Hasenack]

maas 2.5.0-7442-gdf68e30a5-0ubuntu1~18.04.1
curtin 18.1-51-gb812ae80-0ubuntu2~18.04.1
bionic

Using the above maas, I deployed a bionic VM (with uefi boot) using zfs on root. It worked, but to my surprise, the running kernel is an aws one:
root@zfstest:~# uname -a
Linux zfstest 4.18.0-1006-aws #7~18.04.2-Ubuntu SMP Fri Nov 30 22:17:45 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

The generic kernel is also installed, though:
root@zfstest:~# dpkg -l|grep linux-image
ii linux-image-4.15.0-42-generic 4.15.0-42.45 amd64 Signed kernel image generic
ii linux-image-4.18.0-1006-aws 4.18.0-1006.7~18.04.2 amd64 Linux kernel image for version 4.18.0 on 64 bit x86 SMP
ii linux-image-generic 4.15.0.42.44 amd64 Generic Linux kernel image

[Lee Trager (ltrager)]

I've confirmed this is happening however I believe this is a bug in Curtin instead of MAAS. MAAS is telling Curtin to install linux-signed-generic and not the AWS kernel.

[Ryan Harper (raharper)]

Curtin does not specific which kernel to install. Rather MAAS does, and if it doesn't specify a kernel, we use linux-generic (or linux-signed-generic.

however, this is not even when we install the kernel, rather curtin installs zfs and dependencies; for the zfs module, if it;'s not present in the image, curtin will install 'linux-image-$(uname -r)';

Can you enable debug so we can see the verbose logging; that should provide more information as to how it got selected.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

[Launchpad Janitor (janitor)]

[Expired for curtin because there has been no activity for 60 days.]