Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1597518
Description of problem: ds-replcheck command returns traceback errors against ldif files having garbage content when run in offline mode Version-Release number of selected component (if applicable): 389-ds-base-1.3.8.4-3.el7.x86_64 How reproducible: Always Steps to Reproduce: # ds-replcheck -v -M a.ldif -R b.ldif Performing offline report... Gathering all the DN's... Gathering the database RUV's... Traceback (most recent call last): File "/usr/bin/ds-replcheck", line 1290, in <module> main() File "/usr/bin/ds-replcheck", line 1279, in main do_offline_report(opts, OUTPUT_FILE) File "/usr/bin/ds-replcheck", line 575, in do_offline_report opts['master_ruv'] = get_ldif_ruv(MLDIF, opts) File "/usr/bin/ds-replcheck", line 417, in get_ldif_ruv result = ldif_search(LDIF, opts['ruv_dn']) KeyError: 'ruv_dn' I am getting traceback if I have garbage content in ldif files. # cat a.ldif dsfcdfdfdef dsfcdfdsfsfds Actual results: the command crashes Expected results: The command should not report any trackback errors and report that the files have invalid content or some proper error message. Additional info: This bug was found while verifying https://bugzilla.redhat.com/show_bug.cgi?id=1556803
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1597518
Metadata Update from @mreynolds: - Issue assigned to mreynolds
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.3.8 (was: 0.0 NEEDS_TRIAGE)
https://pagure.io/389-ds-base/pull-request/49841
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to review (was: None)
Metadata Update from @spichugi: - Custom field reviewstatus adjusted to ack (was: review)
60cb520 master
1.3.8
commit 878bf89
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/2899
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)
Login to comment on this ticket.