Bug 474043 - Updates are not applied during replica creation
Summary: Updates are not applied during replica creation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: freeIPA
Classification: Retired
Component: ipa-server
Version: 1.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 453489
TreeView+ depends on / blocked
 
Reported: 2008-12-01 20:34 UTC by Rob Crittenden
Modified: 2015-01-04 23:35 UTC (History)
4 users (show)

Fixed In Version: freeipa-2.0.0-1.fc15
Clone Of:
Environment:
Last Closed: 2012-03-27 07:14:03 UTC
Embargoed:


Attachments (Terms of Use)
patch to fix bug (924 bytes, patch)
2008-12-01 20:38 UTC, Simo Sorce
no flags Details | Diff

Description Rob Crittenden 2008-12-01 20:34:16 UTC
Description of problem:

The LDAP updates are not being applied when a replica is created. This is ok for some of them because they be replicated over during the replica creation but anything outside of the base will not be applied, such as plugin configurations.

A call to ds.apply_updates() should be done once the initial replication is done.

Comment 1 Simo Sorce 2008-12-01 20:37:13 UTC
Working on it

Comment 2 Simo Sorce 2008-12-01 20:38:29 UTC
Created attachment 325292 [details]
patch to fix bug

Added ds.apply_updates() right before restarting services.

Comment 3 Jenny Severance 2008-12-03 19:42:04 UTC
Can someone give an example of what updates would be missing on the replica if ds.apply_updates was not executed before restarting services?
Thanks

Comment 4 Rob Crittenden 2008-12-03 20:27:50 UTC
Look for an index for the attribute ntUniqueId. The dn is:

cn=ntUniqueId,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config

Comment 5 Jenny Severance 2008-12-03 20:33:35 UTC
thanks again Rob!

Comment 6 Jenny Severance 2008-12-03 20:36:04 UTC
Fix Verified:

Search after successful replica installation:

[root@jennyv4 yum.repos.d]# ldapsearch -x -h `hostname` -p 389 -D "cn=Directory Manager" -w Secret123 -b "cn=ntUniqueId,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config"
# extended LDIF
#
# LDAPv3
# base <cn=ntUniqueId,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# ntUniqueId, index, userRoot, ldbm database, plugins, config
dn: cn=ntUniqueId, cn=index, cn=userRoot, cn=ldbm database, cn=plugins, cn=con
 fig
objectClass: top
objectClass: nsIndex
cn: ntUniqueId
nsSystemIndex: false
nsIndexType: eq
nsIndexType: pres

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1


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