Descriptioncamorris@redhat.co
2023-05-02 19:58:48 UTC
Description of problem:
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.
Version-Release number of selected component (if applicable):
17.1
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
system hostname is used at identifier
Expected results:
Have a unique UUID instead
Additional info:
Related to blueprint: https://review.opendev.org/q/topic:bp%252Fstable-compute-uuid
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Red Hat OpenStack Platform 17.1.3 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2024:2741