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:
If the instance name contains 'slapd-' anywhere in the name, dsctl doesn't work with the instance.

Version-Release number of selected component (if applicable):
389-ds-base-1.4.2.4-4.module+el8.2.0+4930+d4051b3a.x86_64


How reproducible:
always

Steps to Reproduce:
1. Create an instance with 'slapd-' in the name (doesn't matter if it's in the beginning or in the middle)
2. Try to use dsctl with this instance


Actual results:
[root@server-rhel8 ds]# dsctl --list
slapd-server-nsslapd-test

[root@server-rhel8 ds]# dsctl -v slapd-server-nsslapd-test status
DEBUG: The 389 Directory Server Administration Tool
DEBUG: Inspired by works of: ITS, The University of Adelaide
DEBUG: Called with: Namespace(func=<function instance_status at 0x7f6ef1096950>, instance='slapd-server-nsslapd-test', json=False, list=False, remove_all=False, verbose=True)
DEBUG: list instance not found in /etc/dirsrv/slapd-server-nstest/dse.ldif: server-nstest

ERROR: No such instance 'slapd-server-nsslapd-test'
ERROR: Unable to access instance information. Are you running as the correct user? (usually dirsrv or root)


Expected results:
dsctl should be able to control such instance.

Additional info:

Build tested: 389-ds-base-1.4.2.4-7.module+el8.2.0+5670+0b8b1c2e.x86_64

# dsctl slapd-server-nsslapd-test status
Instance "server-nsslapd-test" is running

Marking as VERIFIED.

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/RHBA-2020:1703