[2.1] When min-hwe kernel is hwe-16.04, it fails to deploy Trusty with unfriendly error message.

[Jason Hobbs]

When selecting minimum kernel, I have both "(xenial) hwe-x" and "(xenial) hwe-16.04" options. If I select "hwe-16.04" and try to deploy trusty, it doesn't work, and says no kernel available for trusty that is at least hwe-16.04. If I select hwe-x, it works.

It's confusing to have both, I'm not sure what the difference is, please make one go away.

==========
HWE kernels have changed in Ubuntu, as such MAAS supports both formats:

For Trusty, we continue to use 'hwe-x', but for Xenial, we now use 'hwe-16.04'. This causes an issue for users who set min_hwe_kernel to hwe-16.04 and try to deploy Trusty, because the kernel is not available.

The error message shown is unfriendly and does not really tell the user what he needs to do. While the error message is accurate, it is not user friendly.

"Node failed to be deployed, because of the following error: ['trusty has no kernels available which meet min_hwe_kernel(hwe-16.04).']"

That said, what MAAS could also do, is that if a hwe-16.04 kernel is set as minimum, and you deploy Trusty, it should probably fallback to the latest HWE kernel for trusty, that is hwe-x.

[Andres Rodriguez (andreserl)]

We can't make one go away. Ubuntu has changed the whole concept of HWE kernels and now we need to support both. See https://docs.ubuntu.com/maas/2.1/en/release-notes#important-changes "New HWE and GA kernel naming convention".

Basically:

 - for Trusty, we need to support hwe-x
 - For Xenial, we need to support hwe-16.04

[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