From 406463ef5767f77673e1a2391ca3b4f2596f6956 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aleix=20Ram=C3=ADrez=20Baena?= Date: Tue, 15 Oct 2024 15:54:04 +0200 Subject: [PATCH] M #-: Fix oneprovision command usage (#3083) (cherry picked from commit 1978a9d22f5884e78a07d3eafd128e1a4afbcaf7) --- .../quick_start/operation_basics/provisioning_edge_cluster.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/quick_start/operation_basics/provisioning_edge_cluster.rst b/source/quick_start/operation_basics/provisioning_edge_cluster.rst index 308caa875..1a4efde51 100644 --- a/source/quick_start/operation_basics/provisioning_edge_cluster.rst +++ b/source/quick_start/operation_basics/provisioning_edge_cluster.rst @@ -224,7 +224,7 @@ First, log in to the Front-end node. .. tip:: If you installed the Front-end by following the :doc:`Quickstart with miniONE on AWS <../deployment_basics/try_opennebula_on_kvm>` tutorial, to log into the Front-end you will need to use the key stored in the PEM file that you obtained from AWS. For details, see :ref:`minione_log_in_to_ec2` in that tutorial. -On the Front-end node, use the ``oneadmin`` command to perform the following actions: +On the Front-end node, use the ``oneprovision`` command to perform the following actions: List clusters in the provision: ``oneprovision cluster list``.