Hello, I'm facing the same issue when deploying any node with 14.04 LTS within MAAS version: 2.3.5.
When I run a Release with erase disk, it tries boot from /var/lib/maas/boot-resources/current/ubuntu/amd64/hwe-t/xenial
and then the node is marked as failed.
my temporary workaround is create symbolic link:
cd /var/lib/maas/boot-resources/current/ubuntu/amd64/hwe-t
ln -s /var/lib/maas/boot-resources/current/ubuntu/amd64/generic/xenial/ xenial
Hello, I'm facing the same issue when deploying any node with 14.04 LTS within MAAS version: 2.3.5.
When I run a Release with erase disk, it tries boot from /var/lib/ maas/boot- resources/ current/ ubuntu/ amd64/hwe- t/xenial
and then the node is marked as failed.
my temporary workaround is create symbolic link: maas/boot- resources/ current/ ubuntu/ amd64/hwe- t maas/boot- resources/ current/ ubuntu/ amd64/generic/ xenial/ xenial
cd /var/lib/
ln -s /var/lib/