group.of.nepali.translators team mailing list archive

[Stéphane Graber <stgraber@xxxxxxxxxxxx>]

** Changed in: lxd (Ubuntu Trusty)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1582891

Title:
  SRU of LXD 2.0.1 (upstream bugfix release)

Status in lxd package in Ubuntu:
  Fix Released
Status in lxd source package in Trusty:
  Fix Released
Status in lxd source package in Xenial:
  Fix Released

Bug description:
  LXD upstream released LXC 2.0.1 as a bugfix release with following changelog:
   - Don't fail to start when shmounts can't be mounted, instead fail container startup
   - Invalidate the simplestreams cache on proxy change
   - Write the container's config file on start to the log path directly
   - Fix crash in list due to empty responses (Issue #1903)
   - Fail when removing non-existent profiles (Issue #1886)
   - Document --alias to image import (Issue #1900)
   - Fix "lxc start" and "lxc stop" options (stateful/stateless)
   - Give better error on invalid source stream (simplestreams)
   - Add basic REST API usage example to README.md
   - Fix typo in lxc stop --help
   - Convert lxc-to-lxd to stable supported pylxd API (Issue #1901)
   - Properly log image update failures
   - Better validate and rollback bad images (Issue #1913)
   - Send operation return value through SmartError
   - Fix basic filtering in lxc list (Issue #1917)
   - Tell the user how to launch a container on first start (Issue #1931)
   - Redirect "remote" to "remote:" when not conflicting (Issue #1931)
   - Don't load the LXC config for snapshots (Issue #1935)
   - list: Allow filtering by unset key (Issue #1917)
   - Fix example in lxc launch
   - Update Japanese translation and other po files
   - Fall back to cpuset.cpus on older kernels (Issue #1929)
   - Properly validate the server configuration keys (Issue #1939)
   - Fix daemonConfig handling of storage
   - Don't remove config file on forkmigrate
   - Fix config handling following config validation change
   - Fixed Markdown syntax in documentation
   - Don't fail early when removing disks (Issue #1964)
   - Don't recursively delete devices
   - Don't fail when some unix devices fail to be deleted
   - Use the same config checks for unix-char and unix-block
   - Allow removing when fs object no longer exists (Issue #1967)
   - Do proper logfile expiry (Issue #1966)
   - Make logging a bit more consistent
   - Don't ignore zfs errors
   - Properly update the mode, uid and gid on existing files (Issue #1975)
   - Detect invalid certificate files (Issue #1977)
   - Fix broken apparmor status check
   - Allow on/off as boolean strings
   - Properly validate the container configuration keys (Issue #1940)
   - Don't mask rsync transfer errors
   - Move execPath to a global variable
   - Use custom netcat instead of nc -U for rsync over websocket (Issue #1944)
   - Fix wrong state dir path in migration
   - Don't fail deleting images when the storage delete fails
   - Improve messages in the Japanese translation
   - Add more checks for the criu binary
   - Rework (live) migration tests
   - Make it explicit in documentation that devices on create are optional
   - Properly record the source of all image copies (Issue #2010)
   - Don't mark containers as ERROR while being created (Issue #1988)
   - Cleanup events sent for operations (Issue #1992)
   - Fix ZFS refcounting issues (Issue #1916 and Issue #2013)
   - Propagate snapshot config when copying a snapshot (Issue #2017)
   - Implement lxc config show for snapshots
   - Add Unix socket example to REST API usage.

  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 bugfix release has already been uploaded to Yakkety and automatically backported in the upstream PPAs for all Ubuntu releases. So far without any reported regression.


  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1582891/+subscriptions