-
Epic
-
Resolution: Done-Errata
-
Normal
-
None
-
None
-
Create nova-compute node UUID file
-
False
-
-
False
-
OSPRH-811Red Hat OpenStack 18.0 Greenfield Deployment
-
Committed
-
No Docs Impact
-
To Do
-
OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
-
openstack-ansible-ee-container-1.0.0-17
-
Committed
-
Committed
-
0% To Do, 0% In Progress, 100% Done
-
Release Note Not Required
-
Automated
-
-
-
2023Q4, 2024Q1
This is only affecting the nova-compute service running the libvirt driver. (We can ignore ironic computes)
Greenfield
Generate a random uuid and put into the compute uuid file that it is stored in the hypervisor and visible but read only in nova_compute container under /etc/nova. This will ensure that nova-compute will not generate a new uuid but will use the pre-generated one.
The upstream feature is available in Antelope so this part can be done right away.
Adoption
When adopting from 17.1 there will be a uuid file already generated by the running compute service (downstrem backport pending https://code.engineering.redhat.com/gerrit/q/topic:stable-compute-uuid ) . So during adoption the generated uuid file need to be preserved. Also to keep the greenfield and adopted deployments the same move the file from /var/lib/nova/compute_id to /etc/nova and make it read only for the nova_compute container.
- is blocked by
-
OSPRH-338 Adopt nova compute nodes
- Closed
- relates to
-
OSPRH-20 Stable Compute UUIDs
- Closed
- links to
-
RHBA-2024:135530 OpenStack Operators
- mentioned on