SRU of LXD 2.0.8 (upstream bugfix release)

[Stéphane Graber]

LXD upstream released LXD 2.0.6 as a bugfix release with following changelog:
 - Support for container specific uid/gid maps (see userns-idmap.md)
 - appveyor: Add config to git (Issue #2537)
 - appveyor: Cleanup appveyor.yml before modifications
 - appveyor: Create archive with platform specifier in its name
 - appveyor: Do verbose testing for test names and timings
 - appveyor: Publish compiled binaries for download
 - client: Rework progress handling
 - doc: Add hacking guide (debugging.md)
 - doc: Add official Windows support in README
 - doc: Bump liblxc version required in README
 - doc: Sort API endpoints in rest-api.md
 - doc: Update README to specify docker installation details
 - doc: Update requirements, we actually require 2.0.0 or higher
 - doc: Use consistent method ordering in rest-api.md
 - extra/bash: Allow dash in parameters to lxc-client bash-completion
 - extra/bash: Fix _lxd_profiles in lxc-client bash-completion
 - extra/lxc-to-lxd: Better output with no container
 - extra/lxc-to-lxd: Check that source path exists (disk) (Issue #2572)
 - extra/lxc-to-lxd: Consistent logging
 - extra/lxc-to-lxd: Don't fail dry-run with runnning containers
 - extra/lxc-to-lxd: Drop dependency on pylxd
 - extra/lxc-to-lxd: Fix lxdpath handling
 - extra/lxc-to-lxd: Formatting
 - extra/lxc-to-lxd: Migrate lxc.aa_profile if set
 - extra/lxc-to-lxd: Print summary and proper exit code
 - lxc/copy: Don't use the operation as a marker of success
 - lxc/copy: Wait on the source operation too
 - lxc/delete: update help text
 - lxc/exec: Set term to "dumb" on windows (Issue #2288)
 - lxc/finger: update help text
 - lxc: Fix tests on Windows/Mac
 - lxc/list: Fix typo in help message
 - lxc/remote: Fix remote add with Go tip
 - lxc/restore: update help text
 - lxc: Use .yaml as the yaml extension in examples
 - lxd/certificates: Export all documented certificate fields
 - lxd/containers: Add /snap/bin to PATH even if only /snap exists
 - lxd/containers: Also clean up apparmor stuff in OnStart when something fails
 - lxd/containers: Attach to userns on file operations
 - lxd/containers: Be more verbose on mkdir failure
 - lxd/containers: Better handle concurent stop/shutdown
 - lxd/containers: Catch and return more errors in OnStop
 - lxd/containers: Clarify container delete failure error
 - lxd/containers: Don't destroy ephemeral container on restart (Issue #2555)
 - lxd/containers: Don't double delete ephemeral containers
 - lxd/containers: Don't show invalid logs
 - lxd/containers: Fix forkmount to work with 4.8 and higher
 - lxd/containers: Fix invalid filename of metadata on export (Issue #2467)
 - lxd/containers: Improve config validation on update
 - lxd/containers: Improve container error handling
 - lxd/containers: Improve container locking mechanism (Issue #2612)
 - lxd/containers: log OnStart/OnStop hook errors
 - lxd/containers: More reliable container autostart (Issue #2469)
 - lxd/containers: Only load kernel modules if not loaded
 - lxd/containers: Properly validate CPU allowance
 - lxd/containers: Properly validate memory limits (Issue #2483)
 - lxd/containers: Record the err from go-lxc
 - lxd/containers: Remove legacy code from OnStop
 - lxd/containers: Remove unused code
 - lxd/containers: Save properties on publish
 - lxd/containers: Set LXC loglevel to match daemon (Issue #2528)
 - lxd/containers: Skip leading whitespace in raw.lxc
 - lxd/containers: Start storage when necessary in stateful start
 - lxd/containers: Timeout container freeze on stop
 - lxd/images: Detect out of disk space unpack errors (Issue #2201)
 - lxd/images: Don't make unnecessary image copies (Issue #2508)
 - lxd/images: Don't update images at all if interval is 0
 - lxd/images: Store the simplestreams cache to disk (Issue #2487)
 - lxd/init: Detect zfs kernel support
 - lxd/init: Ignore ZFS if in a container
 - lxd/main: Immediately exit when no DB in activateifneeded
 - lxd/migration: Fix a race for collecting logs
 - lxd/migration: Remove debugging by file creation
 - lxd/migration: Start migration storage at the right time (Issue #2505)
 - lxd/storage: Fix 10s delay on removing used ZFS images (Issue #2617)
 - lxd/storage: Freeze before copying in dir backend
 - lxd/storage: Simplify rsync code
 - shared/certificates: Be more thorough when parsing ip addr
 - shared: Disable keepalives in http.Transports
 - shared: Move Linux specific tests away (Issue #2449)
 - shared/simplestreams: Cleanup unused properties
 - tests: Better fix LXD_DEBUG
 - tests: Cleanup leftover containers
 - tests: Don't depend on main.sh for filemanip
 - tests: Implement LXD_VERBOSE
 - tests: Reduce verbosity under LXD_DEBUG
 - travis: Run the client tests
 - travis: Update to match Jenkins Go versions

Just like Ubuntu itself, upstream releases long term support releases, as is 2.0 and then periodic point releases including all the accumulated bugfixes.

Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support.

This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to trusty-backports as well, making sure we have the same version everywhere.

[Adam Conrad (adconrad)]

Hello Stéphane, or anyone else affected,

Accepted lxd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxd/2.0.6-0ubuntu1~ubuntu16.04.1 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 on 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!

[Stéphane Graber (stgraber)]

LXD 2.0.6 is bad, it will accidentally convert some containers from unprivileged to privileged on upgrade (only affects existing containers) and may also inadvertently remap containers on migration.

Upstream will be releasing a new LXD 2.0.7 release shortly to address this (along with a LXD 2.6.1 release).

[Stéphane Graber (stgraber)]

We released 2.0.7 and 2.0.8 to fix a number of regressions:
 - extra/bash: Better parse containers list
 - lxc/copy: Make container copy more robust (Issue #2640)
 - lxd/containers: Don't assign idmaps to privileged containers
 - lxd/containers: Don't break when parsing old containers
 - lxd/containers: Don't double apply templates
 - lxd/containers: Fix concurrent map iteration+modification
 - lxd/containers: Fix idmap handling of pre-idmap containers (Issue #2644)
 - tests: Add tests for file templating (Issue #2642)
 - Don't grab addresses from public remotes

I've uploaded an updated package to the queue.

[Martin Pitt (pitti)]

Hello Stéphane, or anyone else affected,

Accepted lxd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxd/2.0.8-0ubuntu1~ubuntu16.04.1 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 on 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!

[Stéphane Graber (stgraber)]

I ran extensive testing of 2.0.8 back when uploading it, we've then had users run it for the past week or so and I've just run some extra manual tests on it now.
That combined with succesful autopkgtest run, means that I'm happy with that SRU.

[Launchpad Janitor (janitor)]

This bug was fixed in the package lxd - 2.0.8-0ubuntu1~ubuntu16.04.1

---------------
lxd (2.0.8-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.8) (LP: #1644377)
    - Don't grab addresses from public remotes

lxd (2.0.7-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.7) (LP: #1644377)
    - extra/bash: Better parse containers list
    - lxc/copy: Make container copy more robust
    - lxd/containers: Don't assign idmaps to privileged containers
    - lxd/containers: Don't break when parsing old containers
    - lxd/containers: Don't double apply templates
    - lxd/containers: Fix concurrent map iteration+modification
    - lxd/containers: Fix idmap handling of pre-idmap containers
    - tests: Add tests for file templating

lxd (2.0.6-0ubuntu1~ubuntu16.04.1) xenial; urgency=medium

  * New upstream bugfix release (2.0.6) (LP: #1644377)
    - Support for container specific uid/gid maps (see userns-idmap.md)
    - appveyor: Add config to git
    - appveyor: Cleanup appveyor.yml before modifications
    - appveyor: Create archive with platform specifier in its name
    - appveyor: Do verbose testing for test names and timings
    - appveyor: Publish compiled binaries for download
    - client: Rework progress handling
    - doc: Add hacking guide (debugging.md)
    - doc: Add official Windows support in README
    - doc: Bump liblxc version required in README
    - doc: Sort API endpoints in rest-api.md
    - doc: Update README to specify docker installation details
    - doc: Update requirements, we actually require 2.0.0 or higher
    - doc: Use consistent method ordering in rest-api.md
    - extra/bash: Allow dash in parameters to lxc-client bash-completion
    - extra/bash: Fix _lxd_profiles in lxc-client bash-completion
    - extra/lxc-to-lxd: Better output with no container
    - extra/lxc-to-lxd: Check that source path exists (disk)
    - extra/lxc-to-lxd: Consistent logging
    - extra/lxc-to-lxd: Don't fail dry-run with running containers
    - extra/lxc-to-lxd: Drop dependency on pylxd
    - extra/lxc-to-lxd: Fix lxdpath handling
    - extra/lxc-to-lxd: Formatting
    - extra/lxc-to-lxd: Migrate lxc.aa_profile if set
    - extra/lxc-to-lxd: Print summary and proper exit code
    - lxc/copy: Don't use the operation as a marker of success
    - lxc/copy: Wait on the source operation too
    - lxc/delete: update help text
    - lxc/exec: Set term to "dumb" on windows
    - lxc/finger: update help text
    - lxc: Fix tests on Windows/Mac
    - lxc/list: Fix typo in help message
    - lxc/remote: Fix remote add with Go tip
    - lxc/restore: update help text
    - lxc: Use .yaml as the yaml extension in examples
    - lxd/certificates: Export all documented certificate fields
    - lxd/containers: Add /snap/bin to PATH even if only /snap exists
    - lxd/containers: Also clean up apparmor stuff on failure in OnStart
    - lxd/containers: Attach to userns on file operations
    - lxd/containers: Be more verbose on mkdir failure
    - lxd/containers: Better handle concurent stop/shutdown
    - lxd/containers: Catch and return more errors in OnStop
    - lxd/containers...

[Stéphane Graber (stgraber)]

The verification of the Stable Release Update for lxd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.