backward incompatible db migration changes
Bug #1443606 reported by
Ivar Lazzaro
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
Fix Released
|
High
|
Ivar Lazzaro | ||
Bug Description
Some patches introduced backward incompatible DB migration changes. This happened because of unnamed constraints introduced in the past that are trickier to modify when we need to.
So far we have been removing those constraints by modifying the original migration file in a backward incompatible way, but since we have the requirement to backport many of the Kilo features in Juno we should use proper migration techniques instead.
List of affected patches (update in progress):
https:/
https:/
| Changed in group-based-policy: | |
| assignee: | nobody → Ivar Lazzaro (mmaleckk) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to group-based-policy (master) | #1 |
| Changed in group-based-policy: | |
| status: | New → In Progress |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to group-based-policy (master) | #2 |
| Changed in group-based-policy: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to group-based-policy (stable/juno) | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to group-based-policy (stable/juno) | #4 |
| tags: | added: in-stable-juno |
| Changed in group-based-policy: | |
| importance: | Undecided → High |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/