migration default value not being applied to dbase
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Eugene Nikanorov |
Bug Description
I have a private repo that is a few weeks behind the upstream, and was having problems stacking. Initially it was failing in one of the migrations, so I changed the SQLAlchemy version to 0.8.4 and alembic to 0.6.5 and retried (clean database).
What I saw was that the migration worked, but later a router create failed. It was complaining that the enable_snat field was not specified and did not have a default value. Checking in the migrations, I saw that 128e042a2b68_
I changed the migration file to use server_
Not sure if we should just apply this change to the existing migration file or if some other action is needed.
Changed in neutron: | |
assignee: | Sergey Kolekonov (skolekonov) → Eugene Nikanorov (enikanorov) |
Changed in neutron: | |
milestone: | none → juno-2 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-2 → 2014.2 |
has the same issue: 40b0aff0302e_ mlnx_initial. py