clusterctl provision reinstall

Reinstall a node set from the network

Synopsis

Reinstall nodes: configure the network boot, set the machines to boot from the network once, remove their host keys, and reset them.

This destroys everything on the nodes. Before it asks, it resolves every node’s address, boot path, service processor and BMC credential, checks that each boot path exists on the PXE host, and asks Slurm whether the nodes run jobs, so that nothing is changed for a set that would stop half way. It refuses protected hosts, lists each boot path with its nodes, and above the configured host count asks for the count to be typed back.

A node that Slurm reports running a job, or cannot say about, is refused unless –lose-jobs is given; –force gets past a protected host, not this check. With –no-reset nothing is reset, so Slurm is not asked, and each node reinstalls at its next network boot.

The boot override is set over Redfish, so a node whose bmc.order does not start with redfish is refused.

When a step fails, the boot links and boot overrides of every node that was not reset are removed again. Whatever could not be removed is named, with the commands that remove it.

clusterctl provision reinstall -n exe0001 clusterctl provision reinstall -n @rack:R02 –dry-run

clusterctl provision reinstall [NODESET] [flags]

Options

      --boot-path string   boot configuration to install from (default: from the cluster rules)
  -h, --help               help for reinstall
      --keep-host-keys     leave the host key file alone
      --lose-jobs          go ahead although Slurm reports jobs on the nodes, or cannot say
      --no-reset           configure everything but do not reset the machines

Options 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 yes

clusterctl provision reinstall