After upgrade from 2.x, machine wants to deploy with hwe-x instead of hwe-16.04 because minimum kernel was set

[Jason Hobbs]

This is with maas 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)

There is a warning on my nodes page that says "ubuntu xenial is configured as the commissioning release but it is not selected for download".

But, I have xenial images synced:

http://paste.ubuntu.com/25674740/

http://paste.ubuntu.com/25674736/

I'm also getting errors when deploying with juju: {"min_hwe_kernel": ["hwe-x is not a usable kernel."]}

[Andres Rodriguez (andreserl)]

Hi Jason,

I think that the message is just an spurious failure.

AS far as the kernel, Xenial+ has changed the kernel naming convention and hwe-x is not used for xenial. As such, you need to deploy the machine with hwe-16.04, so that is not really a bug.

Have you set the minimum HWE kernel to hwe-x on the machine and trying to deploy xenial? that could be the reason why it is failing.

[Jason Hobbs (jason-hobbs)]

Is my MAAS missing an image or not? If not, and that warning is showing, then that's a bug. If it is missing an image, then it's a bug, because it says I have images synced.

In the UI, there is no minimum kernel set. When I do machine read, there is one - hwe-x.

http://paste.ubuntu.com/25674782/

Is that a UI bug that it's not showing? How is it being set to hwe-x if that doesn't exist?

[Andres Rodriguez (andreserl)]

Is this an upgrade? Can you check what URL you are using for the streams ? Are you using v2 or v3 for the streams?

[Andres Rodriguez (andreserl)]

Also, can you deploy the machine without Juju ? what happens when youdeploy the machine without juju.

[Jason Hobbs (jason-hobbs)]

streams config is here:
http://paste.ubuntu.com/25674740/

Yes it's an upgrade, this is a long running maas we've upgraded many times.

[Andres Rodriguez (andreserl)]

I think I know what the issue is:

Since this is an upgrade, the machine was previously set to 'hwe-x'. When the deployment happens it uses 'hwe-x' instead of ga-16.04. SO the solution is for you to provide the correct kernel to the machine as the default kernel.

[Jason Hobbs (jason-hobbs)]

Thanks, set all of my machines to empty minimum kernel and that is allowing things to work now. So, it seems like there is a missing migration to change that value?

[Andres Rodriguez (andreserl)]

IIRC, there's a translation mechanism that should be using hwe-16.04 instead of hwe-x when it sees it set.

[Andres Rodriguez (andreserl)]

ALso, removing the blocker tag as this doesn't seem to be a blocker anymore.

[Jerzy Husakowski (jhusakowski)]

Issue with versions long out of support, not applicable to new versions.