#59 the setup-ds.pl and setup-ds-admin.pl commands give inconsistent feedback
Closed: wontfix None Opened 12 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=690815

Description of problem:
the setup-ds*.pl programs are inconsistent in their feedback when asking to
setup the suffix.  The commentary suggests a suffix containins no space.  The
default value offered, however, contains a space.  See the attached image.  Two
problems here:
1) inconsistency;
2) it is easy to read the commentary, glance at the default, and assume you are
getting a suffix with no space, as shown in the commentary.

Version-Release number of selected component (if applicable):
this was experience with RedHat Directory Server v8.1


How reproducible:
run the setup-ds.pl or the setup-ds-admin.pl programs, and observe the
feedback/interface when it asks about the suffix of the directory tree.

Steps to Reproduce:
1.
2.
3.

Actual results:
the default suffix offered contains a space between the domainname hierarchical
components.

Expected results:
the default suffix offered should not contain a space between the domainname
hierarchical components.

Additional info:

This was fixed in this commit
commit changeset:008edfb/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Thu Jan 14 09:38:28 2010 -0700
Reviewed by: nhosoi (Thanks!)
Branch: HEAD
Fix Description: This patch doesn't fix the problem, but it makes it less li
kely to occur in the future. The problem is that we are not consistent about us
ing normalized DNs everywhere. Without using a normalized DN, it is impossible
to construct a DN containing another DN (e.g. cn="dc=example, dc=com", cn=mappin
g tree, cn=config) that another client can match on. This patch at least forces
setup to use a normalized DN for the suffix.
Platforms tested: RHEL5 x86_64
Flag Day: no
Doc impact: Yes - we will need to document what to do when running into this
problem, as in the workaround in the bug report

Added initial screened field value.

Metadata Update from @nkinder:
- Issue set to the milestone: 1.2.10.rc1

7 years ago

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/59

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)

3 years ago

Login to comment on this ticket.

Metadata