starlingx/docs
Code Issues Proposed changes
c3797554ac
docs/doc/source/node_management/kubernetes/common_host_tasks/unlocking-a-host-using-the-cli.rst
Ron Stone c3797554ac Make filename unique 
Change name of Reboot Limits for Host Unlock

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ic422430f476924875816f6b9935bd3413e109a8d
2022-12-21 09:33:08 -05:00

1.1 KiB
Raw Blame History

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>