[Bug 1737040] Re: [SRU] Update to networking-l2gw 11.0.0 for Pike

Corey Bryant corey.bryant at canonical.com
Thu Feb 1 14:21:08 UTC 2018

This bug was fixed in the package networking-l2gw - 1:11.0.0-0ubuntu1~cloud0

 networking-l2gw (1:11.0.0-0ubuntu1~cloud0) xenial-pike; urgency=medium
   * New upstream release for the Ubuntu Cloud Archive.
 networking-l2gw (1:11.0.0-0ubuntu1) artful; urgency=medium
   * d/gbp.conf: Create stable/pike branch.
   * New upstream release for OpenStack Pike (LP: #1737040).
   * d/control: Align (Build-)Depends with upstream.

** Changed in: cloud-archive/pike
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.

  [SRU] Update to networking-l2gw 11.0.0 for Pike

Status in Ubuntu Cloud Archive:
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in networking-l2gw package in Ubuntu:
  Fix Released
Status in networking-l2gw source package in Artful:
  Fix Released

Bug description:
  Update networking-l2gw in Artful to the correct version for Pike.
  This turns out to be a very minor update to d/control dependencies and officially get the package to version 11.0.0. We have customers asking for this. The prior version was a git snapshot on top of 10.1.0.a2, which was actually very close to 11.0.0.

  [Test Case]
  The following SRU process was followed:

  In order to avoid regression of existing consumers, the OpenStack team
  will run their continuous integration test against the packages that
  are in -proposed.  A successful run of all available tests will be
  required before the proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary
  of the executed tests. The OpenStack team members will not mark
  ‘verification-done’ until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned tests are attached to this bug.


To manage notifications about this bug go to:

More information about the Ubuntu-openstack-bugs mailing list