Test that expand, migrate, contract repos have the same number of steps
Bug #1615020 reported by
Dolph Mathews
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Low
|
Dolph Mathews |
Bug Description
To ensure that each of the 3 new migration repositories contain the same number of steps, we should introduce a test to catch developers attempting to introduce a new step to any one of the new repos, without introducing no-op steps to all of them.
Upon failure, the test should explain to developers that they need to add no-op migrations to the other repositories, and the motivation for doing so (e.g. making it easy for us to prevent deployers from breaking their databases).
summary: |
- Test that expand, migrate, contract migration repos have the same number - of migrations + Test that expand, migrate, contract repos have the same number of steps |
Changed in keystone: | |
assignee: | nobody → Henry Nash (henry-nash) |
Changed in keystone: | |
milestone: | newton-3 → none |
Changed in keystone: | |
milestone: | none → ocata-1 |
To post a comment you must log in.
Bug 1615014 and bug 1615024 also document new assertions regarding rolling upgrades.