From 1cd5436467e27a180d7bebefbc32feafd9286c15 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ji=C5=99=C3=AD=20Suchomel?= Date: Tue, 22 May 2018 16:48:32 +0200 Subject: [PATCH] Fix the argument for cinder-manage command. Correct argument is online_data_migrations, not online-data-migrations. Change-Id: I3bfc9893e004cef4842b7bd432ac5f90cff1349b --- doc/source/upgrade.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/upgrade.rst b/doc/source/upgrade.rst index 562ad91ee64..8be7c7ee9c7 100644 --- a/doc/source/upgrade.rst +++ b/doc/source/upgrade.rst @@ -52,7 +52,7 @@ migrations are banned from schema migration scripts. Instead, the migrations should be done by background process in a manner that doesn't interrupt running services (you can also execute online data migrations with services turned off if you're doing a cold upgrade). In Ocata a new ``cinder-manage db -online-data-migrations`` utility was added for that purpose. Before upgrading +online_data_migrations`` utility was added for that purpose. Before upgrading Ocata to Pike, you need to run this tool in the background, until it tells you no more migrations are needed. Note that you won't be able to apply Pike's schema migrations before completing Ocata's online data migrations. @@ -237,7 +237,7 @@ After maintenance window be supported for one cycle, but should be removed before your next upgrade is performed. -* Since Ocata, you also need to run ``cinder-manage db online-data-migrations`` +* Since Ocata, you also need to run ``cinder-manage db online_data_migrations`` command to make sure data migrations are applied. The tool let's you limit the impact of the data migrations by using ``--max_number`` option to limit number of migrations executed in one run. You need to complete all of the