Change Details

https://docs.openstack.org/nova/latest/admin/compute-node-identification.html

While reimaging cloudvirt1031 today we discovered that nova has some kind of "state" that is lost with the reimage, and that it creates conflicts when registering the hypervisor again with the nova-api. Some upstream docs mention this: https://docs.openstack.org/nova/latest/admin/compute-node-identification.html

While reimaging cloudvirt1031 today we discovered that nova has some kind of "state" that is lost with the reimage, and that it creates conflicts when registering the hypervisor again with the nova-api. Some upstream docs mention this: https://docs.openstack.org/nova/latest/admin/compute-node-identification.html