389-ds-base

#49133 DN normalization should be the same than in RHDS10
Closed: wontfix Opened by mreynolds.

Closed: wontfix
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1411401

Description of problem:
Following this https://bugzilla.redhat.com/show_bug.cgi?id=1410131 that has
been logged for RHDS10, we will need to backport to RHDS9, this ticket:
https://fedorahosted.org/389/ticket/529
so as to have behavior consistent.
Version-Release number of selected component (if applicable):
389-ds-base-11.15...
How reproducible: always.
Steps to Reproduce: see bz 1410131
the failing steps should also fail in RHDS9

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1411401

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1411401

Metadata Update from @mreynolds:
- Custom field type adjusted to defect
- Issue set to the milestone: 1.2.11.33 (was: 0.0 NEEDS_TRIAGE)

Closing as duplicate of

https://pagure.io/389-ds-base/issue/529

Metadata Update from @mreynolds:
- 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/2192

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
Metadata
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.