Description of problem: The host_uuid parameter is commented out in Libvirt's configuration file - /etc/libvirt/libvirtd.conf. The result is all of the Nova compute nodes has the same unique ID. A similar bug was closed Bug 1192123. Version-Release number of selected component (if applicable): python-rdomanager-oscplugin-0.0.8-13.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Install compute nodes Actual results: All of the Nova Compute nodes has the same unique ID. That will cause issues with migrations of instances between hosts. Expected results: Each node have a different unique ID Additional info:
*** Bug 1240322 has been marked as a duplicate of this bug. ***
This is only on virt, correct?
No it's on bare metals also.
host_uuid is commented out in /etc/libvirt/libvirtd.conf by default. I don't follow why we need to change that. The comments above the config option say: ################################################################### # UUID of the host: # Provide the UUID of the host here in case the command # 'dmidecode -s system-uuid' does not provide a valid uuid. In case # 'dmidecode' does not provide a valid UUID and none is provided here, a # temporary UUID will be generated. # Keep the format of the example UUID below. UUID must not have all digits # be the same. So, the output of dmidecode -s system-uuid will be used by default. And you're saying that you're getting the same value from this command on 2 different machines? Can you confirm that when you run this command on 2 different deployed compute nodes, you get the same value? Don't use a cloned VM of a compute node to confirm this. You can also ask virsh directly for the uuid value: # virsh sysinfo The uuid value is shown in the output.
This problem though persists in former installers doens't reproduce all the times in the director. Perhaps the Directors different installation method fixed the problem
Can you confirm this is no longer an issue (installed with OSP-director)
After some rechecking I've found the root cause of this issue, libvirt's system UUID is been set by the output of the command 'dmidecode -s system-uuid'. In my case I have two servers that are in the same chassis, both have the same UUID. From what I can say, this is not a bug in the installer, but a bug in libvirt.