Redeploying an existing hypervisor with the same hostname results in nova-compute startup error

[Pierre Riteau]

Starting with 2023.1, there were changes to the Nova compute node identification process: https://docs.openstack.org/nova/latest/admin/compute-node-identification.html

If a hypervisor is redeployed after wiping its nova_compute Docker volume and the hostname is kept the same, the nova_compute container will fail to start with the following error:

    nova.exception.InvalidConfiguration: No local node identity found, but this is not our first startup on this host. Refusing to start after potentially having lost that state!

Kolla Ansible needs support for injecting the compute node UUID into the /var/lib/nova/compute_id file.

[Matt Crees (mattcrees)]

Workaround for now:

Find the id from the database:

``select uuid from compute_nodes where hypervisor_hostname='<hostname>';``

Add this to a file under ``/mnt/nova/compute_id`` where ``/mnt/nova/`` is mounted as ``/var/lib/nova`` in the nova-compute container.