This bug was fixed in the package openvswitch - 2.6.1-0ubuntu0.16.10.1~cloud0
---
openvswitch (2.6.1-0ubuntu0.16.10.1~cloud0) xenial-newton; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
openvswitch (2.6.1-0ubuntu0.16.10.1) yakkety; urgency=medium
.
xenial-newton-proposed regression tested OK:
==
Totals
==
Ran: 103 tests in 1048.1681 sec.
- Passed: 97
- Skipped: 6
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 596.4067 sec.
--
You received this bug notification because you are a
This bug was fixed in the package openvswitch - 2.6.1-0ubuntu0.16.10.1
---
openvswitch (2.6.1-0ubuntu0.16.10.1) yakkety; urgency=medium
* New upstream stable release (LP: #1641956).
-- James Page Wed, 15 Mar 2017 16:18:17 +
** Changed in: openvswitch
Testing for xenial-newton/proposed for UCA:
==
Totals
==
Ran: 103 tests in 960.2837 sec.
- Passed: 97
- Skipped: 6
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 541.5963 sec.
** Also affects: cloud-archive
Importance: Undecided
Tempest tests against yakkety-proposed:
==
Totals
==
Ran: 103 tests in 835.9265 sec.
- Passed: 97
- Skipped: 6
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 472.6971 sec.
** Tags removed: verification-needed
** Tags added:
Hello James, or anyone else affected,
Accepted openvswitch into yakkety-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/openvswitch/2.6.1-0ubuntu0.16.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Description changed:
New upstream stable point release for 2.6.x
+
+ v2.6.1 - 01 Nov 2016
+ -
+- Fedora packaging:
+ * A package upgrade does not automatically restart OVS service.
+- Bug fixes
+
Test plan:
For all openvswitch updates, we perform
** Description changed:
New upstream stable point release for 2.6.x
+
+ Test plan:
+
+ For all openvswitch updates, 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
This bug was fixed in the package openvswitch - 2.6.1-0ubuntu1
---
openvswitch (2.6.1-0ubuntu1) zesty; urgency=medium
* New upstream point release (LP: #1641956).
* d/openvswitch-switch.openvswitch-nonetwork.service: Update Unit
definition to ensure that openvswitch starts