#50779 CLI can not process replication conflict entries with spaces in the DN
Closed: wontfix by mreynolds. Opened by mreynolds.

Issue Description

If a conflict entry has a space in he DN then the DN/RDN gets truncated during processing and "no such error" is returned:

[10/Dec/2019:23:03:06.290458611 -0500] conn=57 op=2 SRCH base="cn=my conflict+nsuniqueid=e3f43e81-1bca11ea-95d3bc99-2f841849,dc=example,dc=com" scope=0 filter="(objectClass=ldapsubentry)" attrs="* + aci"
[10/Dec/2019:23:03:06.290528960 -0500] conn=57 op=2 RESULT err=0 tag=101 nentries=1 etime=0.000101864
[10/Dec/2019:23:03:06.290794405 -0500] conn=57 op=3 SRCH base="cn=my" scope=0 filter="(objectClass=*)" attrs="* + aci"
[10/Dec/2019:23:03:06.290815439 -0500] conn=57 op=3 RESULT err=32 tag=101 nentries=0 etime=0.000062415

Commit 912b3549 relates to this ticket

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

Commit 912b354 relates to this ticket

61bba3a6b..35ae7f957 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

d61990570..04c110e92 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- 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/3834

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata