6bab551cd8
This patch addresses a bug that allows rolling upgrades to be run out of order and without first checking if the previous command has been run to a higher version before hand. Change-Id: I55fa4f600d89f3a2fb14868f6886b52fd1ef6c6b Closes-Bug: 1615014
8 lines
303 B
YAML
8 lines
303 B
YAML
---
|
|
fixes:
|
|
- |
|
|
[`bug 1615014 <https://bugs.launchpad.net/keystone/+bug/1615014>`_]
|
|
Migration order is now strictly enforced. The ensure upgrade process is
|
|
done in the order it is officially documented and support, starting with
|
|
`expand`, then `migrate`, and finishing with `contract`.
|