openstack
/
keystone
Code Issues Proposed changes

Add New in Pike note to using db_sync check 

This change adds a note (*New in Pike*) to the section for running
db_sync --check to clarify which release this feature was added. This
is similar to other sections in this document that specify the release
that a feature was added in and when it is available.

Change-Id: I7d778fa249997bb24e4563d6960910b93637bbf2
Closes-Bug: #1734549
(cherry picked from commit 756d281490)
This commit is contained in:
Gage Hugo 2017-11-27 16:30:18 -06:00
parent d0721d7cf4
commit 543a71f1de
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/admin/identity-upgrading.rst
View File

@ -239,10 +239,11 @@ authenticate requests normally.
Using db_sync check
~~~~~~~~~~~~~~~~~~~
In order to check the current state of your rolling upgrades, you may run the
command ``keystone-manage db_sync --check``. This will inform you of any
outstanding actions you have left to take as well as any possible upgrades you
can make from your current version. Here are a list of possible return codes.
(*New in Pike*) In order to check the current state of your rolling upgrades,
you may run the command ``keystone-manage db_sync --check``. This will inform
you of any outstanding actions you have left to take as well as any possible
upgrades you can make from your current version. Here are a list of possible
return codes.
* A return code of ``0`` means you are currently up to date with the latest
migration script version and all ``db_sync`` commands are complete.