Bug 1150817
| Summary: | Running db2index with no options breaks replication | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Brian J. Atkisson <batkisso> | |
| Component: | 389-ds-base | Assignee: | Noriko Hosoi <nhosoi> | |
| Status: | CLOSED ERRATA | QA Contact: | Viktor Ashirov <vashirov> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 6.0 | CC: | batkisso, ekeck, hgraham, mreynolds, nkinder, pbokoc, rmeggins, sramling | |
| Target Milestone: | pre-dev-freeze | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | 389-ds-base-1.2.11.15-82.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
When running the db2index script with no options, the script failed to handle on-disk RUV entries because these entries have no parent entries. The existing RUV was skipped and a new one was generated instead, which subsequently caused the next replication to fail due to an ID mismatch. This update fixes handling of RUV entries in db2index, and running this script without specifying any options no longer causes replication failures.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1342382 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-21 10:19:54 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1342382 | |||
|
Comment 10
Noriko Hosoi
2016-05-26 17:13:38 UTC
It turned out it was a real bug in import_foreman which was not adjusted when the backend RUV entry was redesigned. 1). Created 4 master and 2 consumer setup 2). Entries synced across all masters and consumers [root@auto-hv-02-guest09 ~]# SUFF="ou=people,dc=passsync,dc=com"; for PORT in `echo "1189 1289"`; do /usr/bin/ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b $SUFF |grep -i dn: | wc -l ; done 2116 2116 3). Stopped dirsrv instances and ran db2index. [root@auto-hv-02-guest09 MMR_WINSYNC]# service dirsrv stop [root@auto-hv-02-guest09 MMR_WINSYNC]# for MMR in `echo "M1 M2 M3 M4 C1 C2"`; do /usr/lib64/dirsrv/slapd-$MMR/db2index; done 4). Started dirsrv instances and checked the no of entries. [root@auto-hv-02-guest09 MMR_WINSYNC]# service dirsrv start [root@auto-hv-02-guest09 MMR_WINSYNC]# SUFF="ou=people,dc=passsync,dc=com"; for PORT in `echo "1189 1289"`; do /usr/bin/ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b $SUFF |grep -i dn: | wc -l ; done 2125 2125 5). Added few entries to masters and checked if all masters/consumers are synced. [root@auto-hv-02-guest09 MMR_WINSYNC]# PORT=1189; SUFF="ou=people,dc=passsync,dc=com"; for PORT in `echo "1189 1289 1389 1489 2189 2289"`; do /usr/bin/ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b $SUFF |grep -i dn: | wc -l ; done 2125 2125 2125 2125 2125 2125 Replication is working fine after running db2index. Hence, marking the bug as Verified. [root@auto-hv-02-guest09 MMR_WINSYNC]# rpm -qa |grep -i 389-ds 389-ds-base-1.2.11.15-85.el6.x86_64 389-ds-base-libs-1.2.11.15-85.el6.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0667.html |