yahoo-eng-team team mailing list archive

[OpenStack Infra <1642212@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/416383
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d5ce8ea0ed6a3b9f748427d1b552fb88ad738545
Submitter: Jenkins
Branch:    master

commit d5ce8ea0ed6a3b9f748427d1b552fb88ad738545
Author: “Richard <csravelar@xxxxxxxxx>
Date:   Tue Jan 3 23:48:21 2017 +0000

    Add --check to keystone-manage db_sync command
    
    This patch adds a new command to the db_sync upgrade commands. --check
    will check the current state of the users upgrade repos and relay info
    back to the user based on what version each command is currently at and
    if the user has any outstanding db_sync commands left to run. It will
    also notify the user if the db_sync commands were not upgraded in order
    
    Closes-Bug: 1642212
    Change-Id: I79d3640a780d624f14059fe311fafa0542c03357


** Changed in: keystone
       Status: In Progress => Fix Released

-- 
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/1642212

Title:
  RFE: keystone-manage db_sync --check

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  In the automation of deployments and upgrades it would be useful to be
  able to check whether there are any database actions outstanding so
  that the action can be determined and executed.

  Effectively I'm thinking something along the lines of this experience:

  Operator (or automation tool) executes: keystone-manage db_sync
  --check

  The tool checks the db state and returns whether there are any
  migrations to execute (ie --expand), whether there is a --migrate
  outstanding, whether there is a --contract outstanding, or any
  combination of the above. If there is nothing left to do, that should
  be reported too.

  Ideally the output should take two forms:

  1 - stdout messages... obviously this is useful when executing this by hand
  2 - return codes... this is very useful when executing via automation tooling

  The return codes need to be actionable - ie I must know which actions
  are required based on the return code with no ambiguity.

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