clusterctl bmc forget

Forget the recorded certificate of a service processor

Synopsis

Remove the recorded certificate fingerprint of a service processor, so that the next connection records whatever it now presents.

Name the nodes, or the service processor as the certificate error names it. The fingerprints about to be dropped are shown and confirmed like any other change, and a protected host is refused without –force.

Run this after a certificate was replaced on purpose. If it changed without anyone replacing it, find out why first: the next connection trusts whatever it is shown and sends the BMC account to it.

clusterctl bmc forget [NODESET | BMC...] [flags]

Options

  -h, --help   help for forget

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 (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, jsonpath=, jq= (default "table")
      --set stringArray     override one configuration value as PATH=VALUE, repeatable
  -y, --yes                 answer the confirmation prompts with yes

clusterctl bmc forget