Rolling upgrades: online schema migration
Bug #1502887 reported by
Grzegorz Grasza
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Wishlist
|
Ruby Loo |
Bug Description
Future incompatible changes in sqlalchemy models, like removing, renaming columns and tables can break rolling upgrades (upgrades when Ironic services are run at different versions simultaneously).
Besides multi-node grenade CI tests, I think we need some unit tests to check for incompatibilities.
Changed in ironic: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
tags: | added: db |
Changed in ironic: | |
assignee: | nobody → Grzegorz Grasza (xek) |
description: | updated |
Changed in ironic: | |
assignee: | Grzegorz Grasza (xek) → Szymon Borkowski (szymon-borkowski) |
Changed in ironic: | |
assignee: | Szymon Borkowski (szymon-borkowski) → Ruby Loo (rloo) |
To post a comment you must log in.
To address this, we could also ban schema changes which cause incompatibilities like drops and alters:
https:/ /github. com/openstack/ nova/blob/ stable/ liberty/ nova/tests/ unit/db/ test_migrations .py#L224- L225