94fd67c34a
Distributed Upgrade Orchestration Process Using the CLI - Modified this topic to include 2 prerequisites Changing Case on file extensions. Updated comments for Patchset 3 Fixed merge conflicts Updated comments for Patchset 4 Fixed merge conflicts Story: 2008055 Task: 42387 Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com> Change-Id: Ia2c44812052c4f70f4742923fa847698cc0d6fa6 Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
22 lines
619 B
ReStructuredText
22 lines
619 B
ReStructuredText
|
|
.. hil1593180554641
|
|
.. _aborting-the-distributed-upgrade-orchestration:
|
|
|
|
==============================================
|
|
Aborting the Distributed Upgrade Orchestration
|
|
==============================================
|
|
|
|
To abort the current upgrade orchestration operation, use the
|
|
:command:`upgrade-strategy abort` command.
|
|
|
|
.. note::
|
|
|
|
The :command:`dcmanager upgrade-strategy abort` command completes the
|
|
current upgrading stage before aborting, to prevent hosts from being left
|
|
in a locked state requiring manual intervention.
|
|
|
|
.. code-block:: none
|
|
|
|
~(keystone_admin)]$ dcmanager upgrade-strategy abort
|
|
|