Neutron fails to initialize with a core plugin not based on the Neutron DB model
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Édouard Thuleau |
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-
[1] https:/
[2] https:/
[3] https:/
[4] https:/
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
The relevant dev ML thread: http:// lists.openstack .org/pipermail/ openstack- dev/2017- June/thread. html#118556