389-ds-base

#50894 dsconf fails to find a valid instance.
Closed: wontfix by mreynolds. Opened by ndemarco.

Closed: wontfix
Reopen Issue

Issue Description

dsconf fails to find an existing configuration instance.
dse.ldif exists.
The instance can be successfully managed using Cockpit 389DS add in.

  dsconf EXAMPLE-COM config get nsslapd-rootdn nsslapdn cn=Directory Manager
  Error: Could not find configuration for instance: EXAMPLE-COM
[root@ipa1 dirsrv]# pwd
/etc/dirsrv/slapd-EXAMPLE-COM/
[root@ipa1 slapd-EXAMPLE-COM]# ll
total 1764
lrwxrwxrwx. 1 root   root        6 Jan  3 20:38 18a51399.0 -> ca.crt
lrwxrwxrwx. 1 root   root       15 Jan  3 20:38 35d0de71.0 -> Server-Cert.crt
-rw-rw----. 1 dirsrv root     1943 Jan  3 20:38 ca.crt
-rw-r-----. 1 dirsrv root    28672 Jan  3 20:42 cert9.db
-rw-------. 1 dirsrv root    36864 Jan  3 20:38 cert9.db.orig
-r--r-----. 1 dirsrv dirsrv   1743 Jan  3 20:39 certmap.conf
-rw-------. 1 dirsrv dirsrv 198978 Feb 11 09:23 dse.ldif
-rw-------. 1 dirsrv dirsrv 198978 Feb 11 09:17 dse.ldif.bak
-rw-------. 1 dirsrv root   159123 Jan  3 20:48 dse.ldif.ipa.0a0666f80f7701da
-rw-------. 1 dirsrv root   195565 Feb  9 16:44 dse.ldif.ipa.d8c02a85a70a440c
-rw-rw----. 1 dirsrv root   195714 Feb  9 16:45 dse.ldif.modified.out
-rw-------. 1 dirsrv root   199796 Feb  9 23:28 dse.ldif.old
-rw-------. 1 dirsrv dirsrv 198978 Feb  9 23:38 dse.ldif.startOK
-rw-r--r--. 1 dirsrv root   230478 Feb  9 23:32 h
-rw-r-----. 1 dirsrv root    36864 Jan  3 20:42 key4.db
-rw-------. 1 dirsrv root    36864 Jan  3 20:38 key4.db.orig
-rw-------. 1 dirsrv root      257 Jan  3 20:38 noise.txt
-r--------. 1 dirsrv dirsrv     67 Jan  3 20:42 pin.txt
-rw-------. 1 dirsrv root       91 Jan  3 20:38 pin.txt.orig
-rw-r-----. 1 dirsrv dirsrv    575 Feb 10 11:10 pkcs11.txt
-rw-------. 1 dirsrv dirsrv    575 Jan  3 20:38 pkcs11.txt.orig
-rw-------. 1 dirsrv dirsrv     41 Jan  3 20:42 pwdfile.txt
-r--------. 1 dirsrv dirsrv     41 Jan  3 20:42 pwdfile.txt.orig
drwxrwx---. 2 dirsrv dirsrv   4096 Feb 10 11:09 schema
-rw-r-----. 1 dirsrv dirsrv   1902 Feb 10 11:10 Self-Signed-CA.pem
-rw-rw----. 1 dirsrv root     2145 Jan  3 20:38 Server-Cert.crt
-rw-rw----. 1 dirsrv root     2166 Jan  3 20:38 Server-Cert.csr
-rw-r-----. 1 dirsrv dirsrv   1804 Feb 10 11:10 Server-Cert-Key.pem
-rw-r-----. 1 dirsrv dirsrv   2248 Feb 10 11:10 Server-Cert.pem
-r--r-----. 1 dirsrv dirsrv  15142 Dec  9 13:03 slapd-collations.conf

Package Version and Platform

  $ ipa --version
  VERSION: 4.8.4, API_VERSION: 2.235
  $ cat /etc/fedora-release
  Fedora release 31 (Thirty One)

Steps to reproduce

  1. Verify dse.ldif is present in

Actual results

  Error: Could not find configuration for instance: EXAMPLE-COM

Expected results

view the configuration for the referenced instance.

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

This is appears to be an issue with the ~/.dsrc file and how the CLI "instance" name varies from the "instance" name in the .dsrc file. This is being fixed in:

https://pagure.io/389-ds-base/issue/50884

As a work around use the exact instance that is in the ~/.dsrc file. So if the file uses [slapd-EXAMLPE-COM], then use it in the CLI: "dsconf slapd-EXAMPLE-COM ....".

Closing this as a duplicate of #50884

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

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

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)
Metadata
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.