-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
None
-
None
-
None
-
rhel-idm-ds
-
0
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Description of a problem
For testing purpose, I've created an instance starting with "slapd-". While the creation went fine, neither the CLI tools nor the Console could be used to manage such instance. # ps -edf | grep DEMO dirsrv 1445 1 0 12:35 ? 00:00:13 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-slapd-DEMO -i /run/dirsrv/slapd-slapd-DEMO.pid # # dsctl slapd-slapd-DEMO stop No such instance 'slapd-slapd-DEMO' Unable to access instance information. Are you running as the correct user? (usually dirsrv or root) # dsctl slapd-DEMO stop No such instance 'slapd-DEMO' Unable to access instance information. Are you running as the correct user? (usually dirsrv or root) #
Version-Release number of the selected component
rpm -q 389-ds-base cockpit-389-ds
389-ds-base-2.6.1-12.el9_6.x86_64 cockpit-389-ds-2.6.1-3.module+el9dsrv+23022+962c3fa5.noarch
Browser (if applicable)
Steps to reproduce
1. Create an instance with a name starting with "slapd-" 2. Try to manage it using CLI or Console
Actual results
Unmanageable instance.
Expected results
CLI and Console should handle such instance names.
Additional information
Javascript Console:
====================
CMD: loadInstanceList: Load the instance list select ==> dsctl -l -j
index.js:15 CMD: setServerId: Test if instance is running ==> dsctl -j DEMO status
index.js:264 FAIL - getAllObjectClasses - err.message ==> {
"result": -1,
"desc": "Can't contact LDAP server",
"errno": 111,
"ctrls": [],
"info": "Connection refused"
}
