starlingx/docs
Code Issues Proposed changes
docs/doc/source/node_management/kubernetes/common_host_tasks/unlocking-a-host-using-the-cli.rst
Stone 0d7d14b0c2 File structure reorg 
Changed names of kubernetes and openstack subdirs, and reorganized index files
for consistency with other docs.

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: I234dd88e500f12e7c68b0e8bc5b68ca6e0875aba
2021-02-22 13:04:19 -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 <reboot-limits-for-host-unlock>.

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>