docs/doc/source/node_management/kubernetes/common_host_tasks/unlocking-a-host-using-the-cli.rst
Ron Stone f125a8b892 Remove spurious escapes (r8,dsR8)
This change addresses a long-standing issue in rST documentation imported from XML.
That import process added backslash escapes in front of various characters. The three
most common being '(', ')', and '_'.
These instances are removed.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
2023-03-01 11:19:04 +00:00

1.1 KiB

Unlock a Host Using the CLI

Unlocking a host brings a locked host into service.

Unlocking first resets the target host to ensure that it starts from a well-known state. The host is then automatically configured, and any required software patches are applied.

The state transition only succeeds if all the necessary configuration components for the host are already in place.

During the unlock operation, the host is rebooted. If the boot process fails, a second reboot is attempted. For some types of boot failure, the number of successive reboot attempts is limited; for more information, see reboot-limits-for-host-unlock-d9a26854590a.

Note

On a Simplex system, any containers (hosted applications) that were stopped by the preceding host-lock operation are started automatically.

  • Run the following command from the controller's command line.

    ~(keystone_admin)$ system host-unlock <hostname>