vpnaas: mitaka db migrations are placed in liberty directory
Bug #1553769 reported by
Akihiro Motoki
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
High
|
Akihiro Motoki | ||
Bug Description
In vpnaas db migration, we don't have 'mitaka' directory, but actually we have mitaka db migrations.
They should be placed in Mitaka directory.
| Changed in neutron: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron-vpnaas (master) | #1 |
| Changed in neutron: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Thierry Carrez (ttx) wrote Fix included in openstack/neutron-vpnaas 8.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1421b1484a77e02
Author: Akihiro Motoki <email address hidden>
Date: Mon Mar 7 02:48:24 2016 +0900
Move db migration added during Mitaka to proper directory
DB migrations related to VPNaaS endpoint groups and Multiple local
subnets were added during Mitaka dev cycle. They are accidently
placed in liberty directory. We can safely move these files
as db migrations do not depend on file paths.
Closes-Bug: #1553769
Change-Id: I54dd86bb302bed