Hi Serge, Martin, As Serge mentioned in #4, this bug will cause breakage if using both "ip netns" and lxc. As I'm sure you're aware, the OpenStack neutron/quantum gateway makes heavy use of the "ip netns" feature, and it's valid to have LXC containers on the server hosting tje quantum gateway.
Given this setup, adding a container to the server hosting the quantum gateway breaks the netns for the DHCP and L3 agents, which leads to all sorts of fun. So, does it make sense to backport this fix to trusty ? If not, then is manually applying https://github.com/lxc/lxc/pull/393/files a valid workaround ? Thanks ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350947 Title: apparmor: no working rule to allow making a mount private To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
