Skip to content

← Production Guide · VM lifecycle

PG-02 · No valid host, with free capacity?

No valid host, with free capacity? Operational lesson: Three places a build can stop before any compute. Read the exact message first.

Operational lesson. Three places a build can stop before any compute. Read the exact message first.

The memo as text

Situation. Builds end in ERROR with no host assigned, while computes have free CPU, memory and disk. The request stopped before any compute was asked.

First checks (read-only):

  1. Computes up and enabled?: openstack compute service list --service nova-compute
  2. Every host mapped to a cell?: nova-manage cell_v2 list_hosts
  3. Placement candidates for the flavor: openstack allocation candidate list --resource VCPU=<n> ...
  4. What the scheduler logged: nova-scheduler.log for the request id of the failed boot

Think before acting:

  • ⚠️ State-changing. Re-enabling a compute makes it schedulable again. Read its disable reason first: it may still apply.
  • ⛔ Avoid. Changing a ratio directly in Placement. The compute usually overrides it on its next update: set ratios and reserved values in nova.conf.

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. Cells v2 and Placement apply to every current release. Lab-verified on OpenStack 2026.1 (all-in-one, Kolla-Ansible): unmapped host, reserved memory, disabled service and a filter. Stale allocations and missing traits were not reproduced. A plain allocation candidate list still shows a disabled compute: add --forbidden COMPUTE_STATUS_DISABLED (Placement API 1.22) to see what Nova sees. The allocation candidate commands need the osc-placement plugin. Ironic is not covered.

LinkedIn kit

Capacity exists. Hypervisors have free CPU, memory and disk. And every build still ends with "No valid host was found".

Before opening a capacity ticket, read the exact message. It tells you where the request stopped:

→ "...There are not enough hosts available." A scheduler filter rejected every host. The scheduler log names it.
→ "No valid host was found." and nothing after: Placement returned no candidate. Look at inventory, allocation ratios, reserved values, disabled computes.
→ "Host '<host>' is not mapped to any cell": the compute exists but was never mapped. Classic after adding hosts.

Three places the request can stop. And the third message does not even say "No valid host".

Runbook: https://github.com/OzarLand/ozarland-academy/blob/main/docs/runbooks/scheduling/no-valid-host-with-free-capacity.md
More memos: https://github.com/OzarLand/ozarland-academy/tree/main/docs/production

#OpenStack #Nova #Placement #CloudOperations #SRE #OzarLand

Source: no-valid-host.yml. Found an error, or does your platform behave differently? Open an issue or see CONTRIBUTING.