Bug 330141 - uuid generator not initialized by import from command line
Summary: uuid generator not initialized by import from command line
Alias: None
Product: 389
Classification: Retired
Component: Database - Import/Export
Version: 1.1.0beta
Hardware: All
OS: All
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
Depends On:
Blocks: 240316 FDS1.1.0
TreeView+ depends on / blocked
Reported: 2007-10-12 21:40 UTC by Rich Megginson
Modified: 2015-12-07 17:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-12-07 17:16:58 UTC

Attachments (Terms of Use)
diffs (1.70 KB, patch)
2007-10-12 21:40 UTC, Rich Megginson
no flags Details | Diff
cvs commit log (198 bytes, text/plain)
2007-10-13 01:50 UTC, Rich Megginson
no flags Details

Description Rich Megginson 2007-10-12 21:40:49 UTC
The unique ID generator is not initialized if import is run from the command
line.  The bad effect of this is that the clock sequence and node fields are all
zeros.  This could lead to duplicate unique IDs being assigned by two different

Comment 1 Rich Megginson 2007-10-12 21:40:49 UTC
Created attachment 226181 [details]

Comment 2 Rich Megginson 2007-10-13 01:50:08 UTC
Created attachment 226271 [details]
cvs commit log

Reviewed by: nkinder (Thanks!)
Files: see diff
Branch: HEAD
Fix Description: https://bugzilla.redhat.com/show_bug.cgi?id=330141#c0
What happens is that the uuid values all look like this:
So the time based part is generally ok, but the clock seq and node ID part are
never initialized, hence 0's for those fields.
The fix is to initialize the unique id generator in the same manner as we do
for the server when it starts up in regular mode, except that we tell the
generator to use the single threaded (st) mode rather than the multi threaded
(mt) mode.
Platforms tested: RHEL5 x86_64
Flag Day: no
Doc impact: no
QA impact: should be covered by regular nightly and manual testing
New Tests integrated into TET: none

Note You need to log in before you can comment on or make changes to this bug.