Bug 330141 - uuid generator not initialized by import from command line
uuid generator not initialized by import from command line
Product: 389
Classification: Community
Component: Database - Import/Export (Show other bugs)
All All
high Severity high
: ---
: ---
Assigned To: Rich Megginson
Viktor Ashirov
Depends On:
Blocks: 240316 FDS1.1.0
  Show dependency treegraph
Reported: 2007-10-12 17:40 EDT by Rich Megginson
Modified: 2015-12-07 12:16 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-07 12:16:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Rich Megginson 2007-10-12 17:40:49 EDT
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 17:40:49 EDT
Created attachment 226181 [details]
Comment 2 Rich Megginson 2007-10-12 21:50:08 EDT
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.