DB check appears to not be working right
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Lance Bragstad |
Bug Description
Using current master of keystone, executing a keystone-manage db_sync --check seems to always return the RC of 2 regardless of the steps previously confirmed. This happens until the contract is done, then it returns 0.
Steps to reproduce:
root@keystone1:/# mysqladmin drop keystone; mysql create keystone
root@keystone1:/# keystone-manage db_sync --check; echo $?
2
root@keystone1:/# keystone-manage db_sync --expand; echo $?
0
root@keystone1:/# keystone-manage db_sync --check; echo $?
2
root@keystone1:/# keystone-manage db_sync --migrate; echo $?
0
root@keystone1:/# keystone-manage db_sync --check; echo $?
2
root@keystone1:/# keystone-manage db_sync --contract; echo $?
0
root@keystone1:/# keystone-manage db_sync --check; echo $?
0
Not getting the right return codes or advise from the check can spell disaster for automation that uses it, or humans following the documented migration process.
Changed in keystone: | |
milestone: | none → pike-3 |
Looks like the `--check` functionality was added in Pike, so this won't need to back ported. Marking this as High since automation projects can't trust the information we provide.