Skip to content

← Production Guide · Compute operations

PG-35 · After a reboot, VMs stay off?

After a reboot, VMs stay off? Operational lesson: A reboot brings back what is written down. Nova does not restart guests by default.

Operational lesson. A reboot brings back what is written down. Nova does not restart guests by default.

The memo as text

Situation. A rebooted compute answers again, but its instances stay SHUTOFF, or run without network while Nova shows ACTIVE.

First checks (read-only):

  1. Instances, once nova-compute is up: openstack server list --all-projects --host <host> --long
  2. Kolla units: did all come back?: systemctl list-units 'kolla-*' --state=failed,inactive,activating
  3. Does Nova resume guests?: grep -rn resume_guests_state /etc/nova/
  4. Interfaces up, expected MTU?: ip -br link ; ip link show <tunnel-if> | grep -o 'mtu [0-9]*'

Think before acting:

  • ⚠️ State-changing. Check with the owner before starting a SHUTOFF instance: one stopped on purpose looks the same.
  • ℹ️ Know this. Until nova-compute is up and has synchronised, Nova still shows the instances ACTIVE, from before the reboot.

Go deeper

This memo is a memory aid. The procedure, with every command, its risk warning and its limits, is in the runbook:

Where this holds. Written from the Nova 2026.1 configuration reference and Kolla-Ansible 2026.1, which does not set resume_guests_state_on_host_boot. Observed on one all-in-one lab: instances SHUTOFF without the option and resumed with it, and an external interface taken down without a reboot. Not observed: a container that does not come back, a lost MTU, a host address on br-ex, a multinode platform. A failed unit of a service disabled after deployment is not the cause: compare with globals.yml. ML2/OVN and DPDK are not covered.

LinkedIn kit

A compute was rebooted for a kernel update. It is back, it answers SSH, nova-compute is up. And every instance on it is SHUTOFF.

Nothing is broken. resume_guests_state_on_host_boot defaults to False: Nova does not start the guests that were running before a host reboot. Someone has to.

The other surprises after a reboot come from the same place: what was never written down.
→ a service that did not come back, and if it is ovs-vswitchd, every instance is cut off
→ an external interface or bond that is DOWN
→ an MTU that was set by hand, months ago, and is back to the default

One caution before starting everything again: an instance that was stopped on purpose before the reboot looks exactly like the others.

Runbook: https://github.com/OzarLand/ozarland-academy/blob/main/docs/runbooks/recovery/after-a-compute-reboot-instances-shutoff-or-without-network.md
More memos: https://github.com/OzarLand/ozarland-academy/tree/main/docs/production

#OpenStack #Nova #Maintenance #CloudOperations #SRE #OzarLand

Source: after-a-compute-reboot.yml. Found an error, or does your platform behave differently? Open an issue or see CONTRIBUTING.