neutron should automatically stamp the database version when it is deployed
Bug #1207402 reported by
Jay Buffington
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
Salvatore Orlando | ||
neutron |
Fix Released
|
High
|
Henry Gessau | ||
Icehouse |
New
|
Undecided
|
Unassigned |
Bug Description
When neutron automatically deploys the database schema it does not "stamp" the version. According to neutron/
Neutron should automatically stamp the version to head when deploys the schema the first time. That way I don't have to determine what version I'm running so that I can do a schema migration.
Changed in neutron: | |
milestone: | none → havana-3 |
Changed in devstack: | |
assignee: | nobody → Salvatore Orlando (salvatore-orlando) |
Changed in devstack: | |
status: | In Progress → Fix Committed |
Changed in neutron: | |
milestone: | havana-3 → havana-rc1 |
Changed in neutron: | |
milestone: | havana-rc1 → none |
tags: | added: havana-rc-potential |
tags: |
added: havana-backport-potential removed: havana-rc-potential |
Changed in devstack: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
assignee: | Salvatore Orlando (salvatore-orlando) → Henry Gessau (gessau) |
Changed in neutron: | |
assignee: | Henry Gessau (gessau) → Akihiro Motoki (amotoki) |
Changed in neutron: | |
assignee: | Akihiro Motoki (amotoki) → Henry Gessau (gessau) |
Changed in neutron: | |
milestone: | none → juno-1 |
Changed in neutron: | |
milestone: | juno-1 → juno-2 |
Changed in neutron: | |
milestone: | juno-2 → juno-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
Hi Jay,
We're already aware of this issue - and it is quite confusing for me too.
Actually, I am leaning towards ensuring Neutron behaves like any other Openstack service, relying solely on migrations for creating the database schema.
This would imply removing the code which auto-generates the schema, and adapting devstack to perform the migration.
Another issue with the current automatic schema generation is that it correctly adds new tables, but does not alter existing tables - so this why I am leaning for it to go.
However we need to see if that is something we can safely target for H-3.
I am assigning this bug to myself; before pushing a patch I will however consult with the community on the best approach to solve this problem.