Submitter: Zuul
Branch:    master

commit 69d0047cfe969da02d44c036fc3c97a1bfdffc19
Author: Armando Migliaccio <>
Date:   Thu Nov 9 12:24:04 2017 -0800

    Do not load default service plugins if core plugin is not DB based
    Some service plugins make the assumption that Neutron is running
    with a datastore (e.g. revision and timestamps). As the datastore
    setup is a responsibility of the Neutron core plugin, checking
    that this is indeed true avoids errors for those plugins that do
    not implement any DB backend (e.g. monolithic OpenContrail plugin).
    Change-Id: I872fa6e3c3925e521150d79bba864101d9a5f648
    Closes-bug: #1700651

** Changed in: neutron
       Status: In Progress => Fix Released

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

  Neutron fails to initialize with a core plugin not based on the
  Neutron DB model

Status in neutron:
  Fix Released

Bug description:
  Since patch [1], Neutron server load a default service plugins list which all 
of them depends on the Neutron DB model. So for a core plugin which implements 
only the NeutronPluginBaseV2 interface [2] and not the NeutronDbPluginV2 
interface [3], most of the service plugins of that list will be initialized 
without any errors (only the timestamp plugin fails to initialize because it 
tries to do DB stuff in its constructor [4] on master (future Pike release)).
  And all API extensions of that service plugins are listed as supported but 
none of them works. Resources are not extended (tag, revision, auto-allocate) 
or some API extensions returns 404 (network-ip-availability or flavors).


To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to