Comment 32 for bug 1701297

If you are affected by this bug, then you have the following options:
a.) upgrade to maas 2.2
 MAAS 2.2 sends 'apparmor=0' to the installation/commissionging kernel command
 line. 2.2 is in -proposed for 16.04, 16.10, 17.04 repositories and
 is already available in artful.

 Alternatively you can use the maas ppa (add-apt-repository ppa:maas/stable).
 Note, however, that updates to that repository are not managed by the same
 Stable Release Updates policy that is applied to the ubuntu release.

b.) cherry pick the commit to your installation.
 The MAAS commit that put 'a' into place is:
   https://git.launchpad.net/maas/commit/?id=df9a79b9dba9
 It is a one line change. You will need to restart the maas region
 controller after applying the change.

c.) add a global 'kernel_parameter' in maas 2.1.5 with 'apparmor=0'.
 **WARNING**: this will copy over the kernel parameter to the installed
 system, thus without further change, installed systems would run without
 apparmor.