[Bug 1648056] Re: Support LXD multiple sub-uid mapping

[Brian Murray]

Hello James, or anyone else affected,

Accepted nova-lxd into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/nova-
lxd/13.2.0-0ubuntu1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nova-lxd (Ubuntu Xenial)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Support LXD multiple sub-uid mapping

Status in OpenStack LXD Charm:
  Fix Released
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in Ubuntu Cloud Archive ocata series:
  Triaged
Status in nova-lxd:
  Fix Released
Status in nova-lxd package in Ubuntu:
  Fix Released
Status in nova-lxd source package in Xenial:
  Fix Committed
Status in nova-lxd source package in Yakkety:
  In Progress
Status in nova-lxd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  By default, all LXD containers will run with the same subuid/subgid range, which means that if a single container is compromised, all containers on the same host are potentially compromised as well.

  [Test Case]
  deploy a nova-lxd based openstack cloud
  boot multiple instances
  they all share the same uid/gid mapping within a host

  boot multiple instances with a flavor property of lxd:isolated
  all containers have different uid/gid mappings within a host

  [Regression Potential]
  Minimal in nova-lxd itself; we're just adding an additional extra-spec and tweaking the container profile if the underlying LXD daemon supports the isolation feature.

  [Original Bug Report]
  LXD 2.0.6 supports use of distinct sub-uid/gid for each running container; nova-lxd has support for this upstream in all stable and master branches so we should update nova-lxd in >= Xenial to support this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-lxd/+bug/1648056/+subscriptions