#50525 nsslapd-defaultnamingcontext does not change when the assigned suffix got deleted.
Closed: fixed 4 months ago by mreynolds. Opened 4 months ago by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1610234

Description of problem:
nsslapd-defaultnamingcontext does not change when the assigned suffix got
deleted.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.8.4-9.el7.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Add a test suffix - "dc=test2,dc=com"

2. Assign the test suffix to the nsslapd-defaultnamingcontext
ldapmodify -x -h localhost -p 389 -D "cn=Directory Manager"  -w Secret123 <<
EOF
dn: cn=config
changetype: modify
replace: nsslapd-defaultnamingcontext
nsslapd-defaultnamingcontext: "dc=test2,dc=com"
EOF

3. delete the suffix :
ldapdelete -x -r -h localhost -p 389 -D "cn=Directory Manager"  -w Secret123
"dc=test,dc=com"

4. Check the value of nsslapd-defaultnamingcontext, it is still the same suffix
which is already deleted.
ldapsearch -x -h localhost -p 389 -D "cn=Directory Manager"  -w Secret123 -b
"cn=config" | grep -i "nsslapd-defaultnamingcontext"
nsslapd-defaultnamingcontext: dc=test,dc=com


Expected results:
Either nsslapd-defaultnamingcontext should be blank OR it should have the other
existing suffix as its value.

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

4 months ago

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

4 months ago

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE)

4 months ago

Commit fb3be04 relates to this ticket

a14dd18..c1e1b80 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

9c64ebd..66969b2 389-ds-base-1.3.10 -> 389-ds-base-1.3.10

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

4 months ago

Login to comment on this ticket.

Metadata
Related Pull Requests