To elaborate a bit more, the apparmor and overlayfs incompatibility has
been a known kernel issue from before 16.04's release and, at this time,
isn't something that is likely to be fixed in 16.04. I'd like to better
understand if something changed in userspace that started tickling the
incompatibility issue. Did MAAS change how it was using AppArmor in the
recent SRU that took it to version 2.1.5?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701297

Title:
  NTP reload failure (unable to read library) on overlayfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to