Bug 1139742 - Using hosted-engine, a host cannot be added due to having the same UUID
Summary: Using hosted-engine, a host cannot be added due to having the same UUID
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-hosted-engine-setup
Version: 3.5
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: 3.5.0
Assignee: Sandro Bonazzola
QA Contact: meital avital
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-09 14:29 UTC by Thomas Keppler
Modified: 2014-09-26 14:12 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-12 07:15:15 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.