From 7c13d749b136f18a47750c0c817c2bf92139156a Mon Sep 17 00:00:00 2001 From: beeankha Date: Mon, 12 Apr 2021 10:56:55 -0400 Subject: [PATCH] Change 'ansible-tower-service' to 'automation-controller-service' --- docs/clustering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/clustering.md b/docs/clustering.md index d13da47ae7..93c2d55ec0 100644 --- a/docs/clustering.md +++ b/docs/clustering.md @@ -131,7 +131,7 @@ For users who wish to manage SSH authentication from controlling instances to is * **Provisioning** - Provisioning Instances after installation is supported by updating the `inventory` file and re-running the setup playbook. It's important that this file contain all passwords and information used when installing the cluster, or other instances may be reconfigured (this can be done intentionally). -* **Deprovisioning** - Tower does not automatically de-provision instances since it cannot distinguish between an instance that was taken offline intentionally or due to failure. Instead, the procedure for de-provisioning an instance is to shut it down (or stop the `ansible-tower-service`) and run the Tower de-provision command: +* **Deprovisioning** - Tower does not automatically de-provision instances since it cannot distinguish between an instance that was taken offline intentionally or due to failure. Instead, the procedure for de-provisioning an instance is to shut it down (or stop the `automation-controller-service`) and run the Tower de-provision command: ``` $ awx-manage deprovision_instance --hostname=