This is an issue with either the kernel or apparmor, hence this bug has been marked a duplicate of such issue.
That said, MAAS 2.1 (and 2.2) is now deprecated, as such, I highly recommend you upgrade to 2.2. Using MAAS 2.2 now has a work around that would prevent this failure.
If you are no upgrade, you have two options:
1. Use "hwe-16.04" as the kernel to deploy the machine.
2. Use apparmor=0 as a kernel paran. This will, however, cause apparmor to be disabled in your deployed machine.
Hi Liam,
This is an issue with either the kernel or apparmor, hence this bug has been marked a duplicate of such issue.
That said, MAAS 2.1 (and 2.2) is now deprecated, as such, I highly recommend you upgrade to 2.2. Using MAAS 2.2 now has a work around that would prevent this failure.
If you are no upgrade, you have two options:
1. Use "hwe-16.04" as the kernel to deploy the machine.
2. Use apparmor=0 as a kernel paran. This will, however, cause apparmor to be disabled in your deployed machine.
Thanks!