[Bug 1664306] Re: [SRU] newton stable releases

[Launchpad Bug Tracker]

This bug was fixed in the package swift - 2.10.1-0ubuntu1

---------------
swift (2.10.1-0ubuntu1) yakkety; urgency=medium

  * d/p/avoid-infinite-loop-while-placing-parts.patch: Dropped
    no longer needed.
  * New upstream stable release for OpenStack Newton. (LP: #1664306)

 -- Chuck Short <zulcss at ubuntu.com>  Wed, 01 Mar 2017 14:19:25 -0500

** Changed in: swift (Ubuntu Yakkety)
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] newton stable releases

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive newton series:
  Fix Committed
Status in ceilometer package in Ubuntu:
  Invalid
Status in cinder package in Ubuntu:
  Invalid
Status in heat package in Ubuntu:
  Invalid
Status in horizon package in Ubuntu:
  Invalid
Status in keystone package in Ubuntu:
  Invalid
Status in neutron package in Ubuntu:
  Invalid
Status in nova package in Ubuntu:
  Invalid
Status in nova-lxd package in Ubuntu:
  Invalid
Status in swift package in Ubuntu:
  Invalid
Status in ceilometer source package in Yakkety:
  Fix Released
Status in cinder source package in Yakkety:
  Fix Released
Status in heat source package in Yakkety:
  Fix Released
Status in horizon source package in Yakkety:
  Fix Released
Status in keystone source package in Yakkety:
  Fix Released
Status in neutron source package in Yakkety:
  Fix Released
Status in nova source package in Yakkety:
  Fix Committed
Status in nova-lxd source package in Yakkety:
  Fix Released
Status in swift source package in Yakkety:
  Fix Released

Bug description:
  Stable release updates for the following packages to support OpenStack
  Newton:

  ceilometer 7.0.2
  cinder 9.1.2
  heat 7.0.2
  keystone 10.0.1
  neutron 9.2.0
  nova 14.0.4
  swift 2.10.1

  Upstream QA process for stable releases is documented here:

  https://docs.openstack.org/project-team-guide/stable-branches.html

  Test plan:

  For all stable point releases, we perform regression testing by juju
  deploying two openstack clouds, one against -proposed and one against
  -updates, and we then run tempest integration smoke tests[1] to verify
  those deployed clouds, and evaluate any differences in results.

  [1] https://github.com/openstack/tempest/blob/master/README.rst

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