Skip to content

← Production Guide · Compute operations

PG-36 · Compute renamed or re-added?

Compute renamed or re-added? Operational lesson: Three records must agree. A healthy container proves nothing: the log says which one differs.

Operational lesson. Three records must agree. A healthy container proves nothing: the log says which one differs.

The memo as text

Situation. After a rename or a reinstall, nova-compute refuses to start, or starts but never gets a resource provider. Nothing is scheduled on it.

First checks (read-only):

  1. The service Nova has for this host: openstack compute service list --host <host> --long
  2. What Placement has for that name: openstack resource provider list --name <hypervisor-hostname>
  3. What the compute says it is: hostname -f ; cat /var/lib/nova/compute_id
  4. The exact refusal, in the log: grep -iE 'refusing to start|Conflicting' nova-compute.log

Think before acting:

  • 🛑 Destructive. Deleting a service or a provider with the wrong ID removes the real one. Prove it is the leftover: no hypervisor, no instance.
  • ⛔ Avoid. Renaming a registered compute. Upstream does not support it: give the compute its old name back.

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. The runbook is a draft, written from the Nova and Placement 2026.1 sources and the upstream Compute Node Identification guide; the compute_id file exists from 2023.1. On a Kolla-Ansible lab the rename was simulated with [DEFAULT] host: nova-compute logged "Possible rename detected" and kept running, the container healthy, the service down. With the compute_id file lost, the container restarts in a loop instead (docker logs). The Placement name conflict was not reproduced. With Kolla-Ansible, read both inside the nova_compute container.

LinkedIn kit

A compute was reinstalled, or its host name went from a short name to an FQDN. Since then, nova-compute refuses to start. Or it starts, shows "up", and no instance ever lands on it.

Nova ties a compute to three records that must agree:
→ the service, known by its host name
→ the compute node, known by a UUID the compute keeps on disk (compute_id)
→ the Placement resource provider, same UUID, named after the hypervisor

Change the name, lose the file, or leave an old provider behind, and one of them disagrees.

Two things to remember. Read the nova-compute log, not the container status: on a lab the container stayed "healthy" while the service was down. And do not fix it by deleting records while instances still run on that host.

Source runbook status: draft.

Runbook: https://github.com/OzarLand/ozarland-academy/blob/main/docs/runbooks/scheduling/compute-renamed-or-re-registered-resource-provider-conflict.md
More memos: https://github.com/OzarLand/ozarland-academy/tree/main/docs/production

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

Source: compute-renamed-or-re-added.yml. Found an error, or does your platform behave differently? Open an issue or see CONTRIBUTING.