[Bug 1705432] Re: hyperv mechanism enabled by default fails in pike

[Corey Bryant]

This was a packaging issue and we released 5.0.0 with Artful/Pike.
Closing as fix released.

** Changed in: charm-neutron-api
       Status: Triaged => Invalid

** Changed in: charm-neutron-api
   Importance: High => Undecided

** Also affects: networking-hyperv (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: networking-hyperv (Ubuntu)
       Status: New => Fix Released

** Changed in: networking-hyperv (Ubuntu)
   Importance: Undecided => High

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

Title:
  hyperv mechanism enabled by default fails in pike

Status in OpenStack neutron-api charm:
  Invalid
Status in networking-hyperv:
  Invalid
Status in networking-hyperv package in Ubuntu:
  Fix Released

Bug description:
  Deployed xenial-pike on arm64. neutron-api is configured with hyperv
  enabled by default.

  plugins/ml2/ml2_conf.ini:mechanism_drivers =
  openvswitch,hyperv,l2population

  However, the service won't start:

  2017-07-20 09:26:20.866 41832 CRITICAL neutron.plugins.ml2.managers
  [-] The 'hyperv =
  hyperv.neutron.ml2.mech_hyperv:HypervMechanismDriver' entrypoint could
  not be loaded for the following reason: ''module' object has no
  attribute 'CAP_PORT_FILTER''.


  Removing the hyperv mechanism driver allows neutron-api service to
  start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-api/+bug/1705432/+subscriptions