Skip to content

Stop and destroy

Impact Critical

Lumo holds a lantern forward and raises a palm in a careful gesture.

Lumo: pause here

This page covers an operation rated Critical in the risk register. Read its risks before you run anything, and try it on a test platform first.

The command lines of kolla-ansible stop and kolla-ansible destroy, which the study files under "dangerous". What each one stops or removes is described in the sections listed under Related.

Caution

The risk register rates both commands Critical: kolla-ansible stop (R15) and kolla-ansible destroy (R16). For destroy, the precaution of R16 is "Never on production; there is no --limit safety net beyond what you pass".

kolla-ansible -i multinode stop --yes-i-really-really-mean-it -t heat --limit control03
kolla-ansible -i multinode destroy --yes-i-really-really-mean-it   # never on production
  • stop honours skip_stop_containers (e.g. -e '{"skip_stop_containers": ["nova_libvirt"]}').
  • R15 — kolla-ansible stop: it stops all Kolla containers on the targeted hosts, and MariaDB then needs mariadb_recovery
  • R16 — kolla-ansible destroy: what it removes on the targeted hosts, the deploy host included
  • Fact sheet E §6 — destroy in detail: destroy.yml, the destroy role and the tools/cleanup-* scripts
  • Fact sheet E §11 — the confirmation guard --yes-i-really-really-mean-it
  • Execution flow §4 — the row stop of the action matrix
  • Fact sheet B §1.8 — item 4: after stop, the next deploy or reconfigure fails until mariadb_recovery is run
  • Database operations — the mariadb_recovery command