The fix for this is just to add these new kernels to conf/meph-v2.yaml as seen in the attached patch.
That can't happen though until a.) there is a linux-lts-wily in 14.04 you can check that at https://launchpad.net/ubuntu/+source/linux-lts-wily b.) there are di images available also The d-i images will arrive first in peopoaws places at: http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-amd64/current/images/ and http://ports.ubuntu.com/dists/trusty-proposed/main/installer-arm64/current/images/ (substitute arch appropriately) And then to be consumed by maas-images as it is, they have to be in -updates at http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-amd64/current/images/ http://ports.ubuntu.com/dists/trusty-updates/main/installer-arm64/current/images/
You'll know theyre in 'b' when you see something like 'wily-netboot' in those indexes.
The fix for this is just to add these new kernels to conf/meph-v2.yaml as seen in the attached patch.
That can't happen though until /launchpad. net/ubuntu/ +source/ linux-lts- wily archive. ubuntu. com/ubuntu/ dists/trusty- proposed/ main/installer- amd64/current/ images/ and ports.ubuntu. com/dists/ trusty- proposed/ main/installer- arm64/current/ images/ archive. ubuntu. com/ubuntu/ dists/trusty- updates/ main/installer- amd64/current/ images/ ports.ubuntu. com/dists/ trusty- updates/ main/installer- arm64/current/ images/
a.) there is a linux-lts-wily in 14.04
you can check that at https:/
b.) there are di images available also
The d-i images will arrive first in peopoaws places at:
http://
http://
(substitute arch appropriately)
And then to be consumed by maas-images as it is, they have to be in -updates at
http://
http://
You'll know theyre in 'b' when you see something like 'wily-netboot' in those indexes.