[1.9.2] Using Xenial Kernel by default to enlist/commission and can't seem to be able to change it

[Larry Michel]

I upgraded from 1.9.1 to 1.9.2 and seeing that the kernel used for enlistment/commissioning is the Xenial kernel.

I have tried to changed it to hwe-t, but it continues to enlist with Xenial kernel.

$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================================-================================-============-===============================================================================
ii maas 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.2+bzr4568-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Larry Michel (lmic)]

clusterd.log file.

[Larry Michel (lmic)]

I don't think this is a dup of 1573046. It's actually very recreatable post install or post upgrade.

I have attached the screenshot to show symptom when this happens. I recreated with both 1.9.2 and 2.0. For that scenario, it uses Xenial even though Trusty and no minimal kernel is selected.

I was actually able to clear it by selecting the hwe-x kernel in the list and Clicking on save. The save operation cleared the list and dropdown came back with no minimal servers selected and a list of available kernel that did not include hwe-x. At that point, I was able to commission the servers (with trusty ephemeral image).

[Larry Michel (lmic)]

This is screenshot after I try to save hwe-x, which ended up clearing the issue.