-
Epic
-
Resolution: Done-Errata
-
Critical
-
None
-
None
-
Stable Compute UUIDs
-
False
-
-
False
-
Committed
-
Committed
-
To Do
-
openstack-nova-27.1.1-18.0.20230930093334.a869ab1.el9ost
-
Committed
-
Committed
-
0% To Do, 25% In Progress, 75% Done
-
-
Enhancement
-
Done
-
Automated
-
-
-
OSPPlanningCycle3, 2023Q1
-
Approved
https://specs.openstack.org/openstack/nova-specs/specs/2023.1/approved/stable-compute-uuid.html
The nova-compute service does not strongly correlate with the unique identifier used to represent itself. In most cases, we use the system hostname as the identifier by which we locate our Service and ComputeNode records in the database. However, hostnames can change (both intentionally and unintentionally) which makes this problematic. The Nova project has long said “don’t do that” although, in reality, we must be less fragile and able to detect and protect against database corruption if it happens.
- is related to
-
OSPRH-117 Create nova-compute node UUID file
- Closed
- relates to
-
OSPRH-11 Link Compute Objects by ID
- Dev Complete
- links to
-
RHBA-2023:116856 Release of components for OSP 18.0
-
RHBA-2024:133297 Release of components for Red Hat OpenStack Services on OpenShift 18.0
1.
|
Stable Compute UUIDs | Closed | Unassigned |