diff options
| author | Zuul <zuul@review.openstack.org> | 2018-02-14 19:14:20 +0000 |
|---|---|---|
| committer | Gerrit Code Review <review@openstack.org> | 2018-02-14 19:14:20 +0000 |
| commit | 9a0742964011ba0df02230f6961e19859fc7d279 (patch) | |
| tree | 64cf3c58c35448a8c9e1d8be623face50441389a | |
| parent | 910f2a3adf6c36091e1d26ceaa6f5c9579849a64 (diff) | |
| parent | 543a71f1de7c69635dd5b257bc5a15b342a1b031 (diff) | |
| download | keystone-9a0742964011ba0df02230f6961e19859fc7d279.tar.gz | |
Merge "Add New in Pike note to using db_sync check" into stable/pike
| -rw-r--r-- | doc/source/admin/identity-upgrading.rst | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/source/admin/identity-upgrading.rst b/doc/source/admin/identity-upgrading.rst index 9a1795b50..687dba4e3 100644 --- a/doc/source/admin/identity-upgrading.rst +++ b/doc/source/admin/identity-upgrading.rst @@ -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. |