Bug 1139742

Summary: Using hosted-engine, a host cannot be added due to having the same UUID
Product: [Retired] oVirt Reporter: Thomas Keppler <thomas.keppler>
Component: ovirt-hosted-engine-setupAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED WONTFIX QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: high    
Version: 3.5CC: bugs, dfediuck, didi, ecohen, gklein, iheim, lveyde, pstehlik, rbalakri, stirabos, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-12 07:15:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thomas Keppler 2014-09-09 14:29:13 UTC 
Description of problem: After running hosted-engine --deploy on one host properly, running it on the second fails with the error that the UUID of the current computer is already in the database.


Version-Release number of selected component (if applicable):


How reproducible: Very


Steps to Reproduce:
1. Use multiple Supermicro based systems (same Board revision)
2. Try to add them into the same hosted-engine setup.

Actual results: The hosted-engine --deploy process fails.


Expected results: The hosted-engine --deploy process succeeds and the following nodes are visible to the engine.

Additional info: Used CentOS 7 with oVirt 3.5 nightly snapshots (through repository).
Comment 1 Thomas Keppler 2014-09-11 06:35:48 UTC 
Workaround (so it seems):
Use uuidgen > /etc/vdsm/vdsm.id to generate a new UUID. For restoring a current oVirt installation, please take measures to backup this file, as this BECOMES your new UUID for this machine.
Comment 2 Sandro Bonazzola 2014-09-12 07:15:15 UTC 
As discussed in mailing list, closing as wontfix since this is a corner case hitting only systems with bugged bioses.

http://lists.ovirt.org/pipermail/users/2014-September/027292.html

Workaround for the issue is available in comment #1.