id: PG-36
category: compute
title: Compute renamed or re-added?
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.

diagram:
  type: compare
  caption: Three records that must agree
  columns:
    - kicker: Nova
      title: The service
      icon: server
      tone: ink
      points:
        - Known by its host name
        - "`compute service list`"
    - kicker: Nova
      title: The compute node
      icon: cpu
      tone: ink
      points:
        - "A UUID, kept on disk in `compute_id`"
        - "`hypervisor list`, API 2.53"
    - kicker: Placement
      title: The resource provider
      icon: database
      tone: ink
      points:
        - Same UUID, named after the hypervisor
        - "`resource provider list`"
  note: >-
    Running instances keep running. They are at risk only if records are deleted while they still run
    there.

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

caution:
  - level: destructive
    text: >-
      Deleting a service or a provider with the wrong ID removes the real one. Prove it is the leftover: no
      hypervisor, no instance.
  - level: avoid
    text: >-
      Renaming a registered compute. Upstream does not support it: give the compute its old name back.

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

runbook:
  path: scheduling/compute-renamed-or-re-registered-resource-provider-conflict.md
  status: draft
  release: "2026.1"
  also:
    - scheduling/placement-allocations-out-of-sync-audit-and-heal.md

scope: >-
  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:
  title: "A compute was renamed. Now nova-compute refuses to start."
  caption: |
    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.
  hashtags: [OpenStack, Nova, Placement, CloudOperations, SRE, OzarLand]
