#50823 dsctl doesn't work with 'slapd-' in the instance name
Closed: wontfix 4 years ago by mhonek. Opened 4 years ago by mhonek.

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:


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.1

4 years ago

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)

4 years ago

Metadata Update from @vashirov:
- Issue set to the milestone: 1.4.1

4 years ago

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

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

Ahhh I missed that. Thanks for clarifying.

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

Metadata Update from @mhonek:
- Issue close_status updated to: None (was: Fixed)

4 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/3877

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

3 years ago

Login to comment on this ticket.

Metadata
Related Pull Requests