dsctl doesn't work with 'slapd-' in the instance name

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/50823

• Created at 2020-01-15 18:35:58 by mhonek (@kenoh)
• Closed at 2020-01-30 13:53:04 as None
• Assigned to mhonek (@kenoh)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1779216

---

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:

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-01-16 17:42:22

Metadata Update from @mreynolds389:

• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Issue set to the milestone: 1.4.1

[389-ds-bot]

Comment from vashirov (@vashirov) at 2020-01-16 17:43:40

Metadata Update from @vashirov:

• Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1779216
• Issue set to the milestone: None (was: 1.4.1)

[389-ds-bot]

Comment from vashirov (@vashirov) at 2020-01-16 17:49:36

Metadata Update from @vashirov:

• Issue set to the milestone: 1.4.1

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-01-23 01:33:02

So doesn't this mean the instance in /etc is called "slapd-slapd-instance"?

[389-ds-bot]

Comment from vashirov (@vashirov) at 2020-01-23 09:50:26

In the reproducer in the description it was called slapd-server-nsslapd-test.

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-01-24 00:23:43

Ahhh I missed that. Thanks for clarifying.

[389-ds-bot]

Comment from mhonek (@kenoh) at 2020-01-30 13:53:03

Commit 52930da0 fixes this issue

[389-ds-bot]

Comment from mhonek (@kenoh) at 2020-01-30 14:02:29

675a605..8d6f8f5 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
6a683f7..9168d3c 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

[389-ds-bot]

Comment from mhonek (@kenoh) at 2020-01-30 14:02:30

Metadata Update from @kenoh:

• Issue close_status updated to: None (was: Fixed)