From fe591c99d3cd7f70e1e7002b4115ca0f73150b32 Mon Sep 17 00:00:00 2001 From: Juan Antonio Osorio Robles Date: Tue, 24 Oct 2017 12:11:22 +0300 Subject: [PATCH] Change mistral commands to use the openstack CLI instead Change-Id: I593c199990d8c46e7442fd4b49d80bea8d6b7d26 --- doc/source/install/post_deployment/fernet_key_rotation.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/source/install/post_deployment/fernet_key_rotation.rst b/doc/source/install/post_deployment/fernet_key_rotation.rst index 17c7b175..fda7b686 100644 --- a/doc/source/install/post_deployment/fernet_key_rotation.rst +++ b/doc/source/install/post_deployment/fernet_key_rotation.rst @@ -7,7 +7,8 @@ Like most passwords in your overcloud deployment, keystone fernet keys are also stored as part of the deployment plan in mistral. The overcloud deplotment's fernet keys can be rotated with the following command:: - mistral execution-create tripleo.fernet_keys.v1.rotate_fernet_keys \ + openstack workflow execution create \ + tripleo.fernet_keys.v1.rotate_fernet_keys \ '{"container": "overcloud"}' Where the value for "container" is the name of the plan (which defaults to @@ -17,7 +18,7 @@ After waiting some time you can verify the output by taking the execution ID from that was the output of the previous command, and issuing the following command:: - mistral execution-get-output EXECUTION_UUID + openstack workflow execution output show EXECUTION_UUID Please note that there must be an overcloud deployment ready and accessible in order to execute this action.