After some discussion on the ML this RFE request. There are quite a few hardware vendors that don't fill in thee systems uuid which leads to vdsm not being installed during host deployment. This problem can be circumvented by using uuidgen instead of relying on dmidecode returning the uuid.
Ref.: http://lists.ovirt.org/pipermail/users/2014-July/025822.html http://lists.ovirt.org/pipermail/users/2014-July/025831.html
(In reply to Douglas Schilling Landgraf from comment #1) > Ref.: > http://lists.ovirt.org/pipermail/users/2014-July/025822.html > http://lists.ovirt.org/pipermail/users/2014-July/025831.html From the reference you created a duplicate of a system, but in order it to be unique you need to remove /etc/vdsm/vdsm.id and probably other system static identities, such as dhcp host id. Then redeploy the host. If you like to move the mass storage device between hosts, you should also put a random uuid within /etc/vdsm/vdsm.id after each clone, this will enable the new host to be detached from its clone, regardless of the host it is being installed.
Hi Alon, You closed the BZ but I still get email asking for more info. Ah, see the checkbox below my typing so this should be the last time :-) Joop