clusterctl provision status
clusterctl provision status
Show where a reinstallation stands
Synopsis
Show, for each node, the boot path its link on the PXE service points at, the power state its service processor reports and whether it answers over ssh yet.
The processors and the nodes are asked at the same time, each within its own bound: fanout.max nodes at once, and bmc.redfish.maxConcurrent processors, or fewer when –fanout is lower.
Every node is listed. A node that does not answer over ssh is shown as such and does not fail the command, since a machine that is reinstalling does not answer. A boot path or a power state that cannot be read is shown as unknown, with the reason in the ERROR column and in the error field of the node in the JSON output, and fails the command: with exit code 3 when a host could not be reached, 2 for a configuration problem such as a missing credential, and 1 when a host refused.
clusterctl provision status [NODESET] [flags]Options
-h, --help help for statusOptions inherited from parent commands
--config strings configuration file or directory to read, repeatable (default: CLUSTERCTL_CONFIG or the search path)
--context string context to act on (default: the current one)
--dry-run report what would be done and change nothing
--fanout int how many hosts to work on at once, at least 1; caps the service processors and the names asked at once too, which fanout.max and CLUSTERCTL_FANOUT do not (default: from the configuration)
--force allow protected hosts, and nodes the inventory does not know, to be touched
-n, --nodes stringArray node set to act on, for example 'exe[1-10],@rack:R02' (default: CLUSTERCTL_NODES)
-o, --output string output format: table, wide, json, yaml, nodeset, name, jq= (default "table")
--progress string how to show the progress of a command on standard error: auto, tty, counter, plain, none (default: CLUSTERCTL_PROGRESS, else auto, a live tree when standard error is a terminal; plain writes lines for a log)
--progress-log string append the progress events of a command to this file, one JSON object per line, created readable by you alone (default: CLUSTERCTL_PROGRESS_LOG; an empty one writes none)
--set stringArray override one configuration value as PATH=VALUE, repeatable
-y, --yes answer the confirmation prompts with yesSEE ALSO
- clusterctl provision - Reinstall nodes end to end