summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorZhijiang Hu <hu.zhijiang@zte.com.cn>2018-04-04 08:39:27 +0800
committerZhijiang Hu <hu.zhijiang@zte.com.cn>2018-04-04 08:39:27 +0800
commit7c7dab2f33becdf3c32ba15e5549207b8e793aac (patch)
treee5920351fa41d252262383051f35ef131f5d3767 /docs
parent899b9d234ad7729f98370a73202538715a6bf760 (diff)
upadate doc about error recovery level 3
Change-Id: Id6957830b0fa036c3b68d3ae1ef545c69cd26dce Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
Diffstat (limited to 'docs')
-rw-r--r--docs/release/installation/recovery.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/release/installation/recovery.rst b/docs/release/installation/recovery.rst
index d61357b3..eb9be8b2 100644
--- a/docs/release/installation/recovery.rst
+++ b/docs/release/installation/recovery.rst
@@ -82,11 +82,10 @@ This basically does kolla-ansible destruction and kolla-asnible deployment.
4. Recovery Level 3
-------------------
-If previous deployment was failed during kolla deploy, but the kolla
-configuration file (/etc/kolla/globals.yml) is present, or if previous
-deployment was successful but the default configration is not what you want
-and it is OK for you to destroy the OPNFV software stack and re-deploy it
-again, then you can try recovery level 3.
+If previous deployment was failed during kolla-ansible deploy(you can confirm
+it by checking /var/log/daisy/api.log) or if previous deployment was successful
+but the default configration is not what you want and it is OK for you to destroy
+the OPNFV software stack and re-deploy it again, then you can try recovery level 3.
For example, in order to use external iSCSI storage, you are about to deploy
iSCSI cinder backend which is not enabled by default. First, cleanup the