Fix incorrect mariadb-recovery task name in error message

Closes-Bug: #2133983

Change-Id: Ib79cd622123d9b6727ab1d674f680b8e2d52ed68
Signed-off-by: Vudn <[email protected]>

Author: VuDn5

ansible/roles/mariadb/tasks/lookup_cluster.yml

@@ -36,7 +36,7 @@
 
     - name: Fail on existing but stopped cluster
       fail:
-        msg: MariaDB cluster exists but is stopped. Please start it using kolla-ansible mariadb_recovery
+        msg: MariaDB cluster exists but is stopped. Please start it using kolla-ansible mariadb-recovery
       when:
         # NOTE(yoctozepto): we allow single-node cluster to start
         - groups[mariadb_shard_group] | length > 1

doc/source/admin/mariadb-backup-and-restore.rst

@@ -127,7 +127,7 @@ pointing to the first node of the cluster:
 
 .. code-block:: console
 
-   kolla-ansible mariadb_recovery -i multinode -e mariadb_recover_inventory_name=controller1
+   kolla-ansible mariadb-recovery -i multinode -e mariadb_recover_inventory_name=controller1
 
 The above procedure is valid also for a disaster recovery scenario. In such
 case, first copy MariaDB backup file from the external source into

doc/source/user/operating-kolla.rst

@@ -240,7 +240,7 @@ containers.
 ``kolla-ansible destroy -i INVENTORY`` is used to clean up containers and
 volumes in the cluster.
 
-``kolla-ansible mariadb_recovery -i INVENTORY`` is used to recover a
+``kolla-ansible mariadb-recovery -i INVENTORY`` is used to recover a
 completely stopped mariadb cluster.
 
 ``kolla-ansible prechecks -i INVENTORY`` is used to check if all requirements