[Bug 1780752] Re: [SRU] ovs 2.9.2

[Albert Damen]

After installing this upgrade, my openstack neutron services didn't start anymore.
Neutron log shows:
2018-10-18 08:08:10.573 16703 CRITICAL neutron [-] Unhandled error: ImportError: No module named compat
...
2018-10-18 08:04:30.302 14895 ERROR neutron   File "/usr/lib/python2.7/dist-packages/ovs/db/custom_index.py", line 12, in <module>
2018-10-18 08:04:30.302 14895 ERROR neutron     from ovs.compat import sortedcontainers
2018-10-18 08:04:30.302 14895 ERROR neutron ImportError: No module named compat

Downgrading openvswitch-common, openvswitch-switch and python-
openvswitch to version python-openvswitch solved the problem.

I found https://bugzilla.redhat.com/show_bug.cgi?id=1619712 which
suggests the issue is due to a change in openvswitch 2.9.1.


** Bug watch added: Red Hat Bugzilla #1619712
   https://bugzilla.redhat.com/show_bug.cgi?id=1619712

** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic

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

Title:
  [SRU] ovs 2.9.2

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in openvswitch package in Ubuntu:
  Fix Released
Status in openvswitch source package in Bionic:
  Fix Committed
Status in openvswitch source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  This release sports mostly bug-fixes and we would like to make sure all of our supported customers have access to these improvements.

  The update contains the following package updates:

     * openvswitch 2.9.2

  [Test Case]
  The following SRU process was followed:

  https://wiki.ubuntu.com/OpenStackUpdates

  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:
https://bugs.launchpad.net/cloud-archive/+bug/1780752/+subscriptions