yahoo-eng-team team mailing list archive

[Jesse Pretorius <jesse.pretorius@xxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: keystone
     Importance: High
         Status: Confirmed


** Tags: sql

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1698900

Title:
  DB check appears to not be working right

Status in OpenStack Identity (keystone):
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1698900/+subscriptions