VPN Migration does not specify correct plugin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
Salvatore Orlando |
Bug Description
The VPN migration (rev: 52ff27f7567a) currently applies to:
neutron.
However, the above plugin is pretty much just a class inheriting from the base db support class, and not useful in practice.
In fact, devstack configures neutron with:
neutron.
As a result, the migration is skipped for the VPN service, and VPN models are auto-generated by Neutron at startup rather than being created by the migration.
This is evident when disabling auto-generation of db models, as reported by the following logs
1) Taken running devstack locally with auto schema generation suppressed: http://
2) Gate failure for https:/
diff --git a/neutron/
index c83804e..41f934d 100644
--- a/neutron/
+++ b/neutron/
@@ -30,7 +30,7 @@ down_revision = '39cf3f799352'
# Change to ['*'] if this migration applies to all plugins
migration_
- 'neutron.
+ 'neutron.
]
Changed in neutron: | |
importance: | High → Critical |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | havana-rc1 → 2013.2 |
Fix proposed to branch: master /review. openstack. org/47920
Review: https:/