Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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://access.redhat.com/errata/RHSA-2018:3127
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