Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1861504
# ds-replcheck -M /tmp/userRoot2ldif -R /tmp/userRoot.ldif -b "dc=example,dc=com" >/tmp/ds-replcheck_11-12.offline ... Traceback (most recent call last): File "/usr/bin/ds-replcheck", line 1394, in <module> main() File "/usr/bin/ds-replcheck", line 1383, in main do_offline_report(opts, OUTPUT_FILE) File "/usr/bin/ds-replcheck", line 687, in do_offline_report diff = cmp_entry(mresult['entry'], rresult['entry'], opts) File "/usr/bin/ds-replcheck", line 450, in cmp_entry diff['dn'] = mentry['dn'] TypeError: 'NoneType' object has no attribute '__getitem__' Fix: @@ -725,6 +726,10 @@ def do_offline_report(opts, output_file=None): missing = False for dn in master_dns: mresult = ldif_search(MLDIF, dn) + if mresult['entry'] is None and mresult['conflict'] is None and not mresult['tombstone']: + # Try from the beginning + MLDIF.seek(0) + mresult = ldif_search(MLDIF, dn) rresult = ldif_search(RLDIF, dn)
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1861504
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue assigned to mreynolds - Issue priority set to: major - Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE) - Issue tagged with: CLI
https://pagure.io/389-ds-base/pull-request/51234
Commit ea39a99e relates to this ticket
444fe6fbf..5e4d1625e 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
6e2e7900b..59a811178 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
49cbd94a0..22d67399b 389-ds-base-1.3.10 -> 389-ds-base-1.3.10
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/4286
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)