In Juno cycle we already merged unconditional db migration and the healing
migration. After the healing migration, all database tables are populated for
all core/service plugins and drivers. I think we no longer need this fix.
I will mark this Invalid.
** Changed in: neutron
Status: In Progress => Invalid
** Changed in: neutron
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1286052
Title:
service_plugins do not work like documented in neutron-db-manage
Status in OpenStack Neutron (virtual network service):
Won't Fix
Bug description:
neutron.conf says for the key "service_plugins":
# List of service plugin entrypoints to be loaded from the
# neutron.service_plugins namespace. See setup.cfg for the entrypoint names of
# the plugins included in the neutron source distribution. For compatibility
# with previous versions, the class name of a plugin can be specified instead
# of its entrypoint name.
#
# service_plugins =
# Example: service_plugins = router,firewall,lbaas,vpnaas,metering
However when using the "Example" service_plugins, neutron-db-manage
errors out on invocation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1286052/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
