-
Bug
-
Resolution: Done-Errata
-
Minor
-
dirsrv-12.2
-
cockpit-389-ds-3.0.6-1.el10dsrv
-
None
-
rhel-idm-ds
-
0
-
devel-ack
-
False
-
False
-
-
None
-
None
-
None
Description of problem:
This is new occurrence of an old bug: https://bugzilla.redhat.com/show_bug.cgi?id=2027835
RHDS Console will fail to load an instance if the DB backup directory ( nsslapd-bakdir ) is set to a non-existing directory.
The Console will show a spinner and won't allow to select any other RHDS instances.
Version-Release number of selected component (if applicable):
- rpm -qa | grep 389-ds
389-ds-base-libs-2.2.7-1.module+el9dsrv+18376+e226feec.x86_64
389-ds-base-2.2.7-1.module+el9dsrv+18376+e226feec.x86_64
cockpit-389-ds-2.2.7-1.module+el9dsrv+18376+e226feec.noarch
How reproducible:
Always
Steps to Reproduce:
1. Change back up directory to non-existing one.
$ dsconf -D "cn=Directory Manager" ldap://localhost:38901 config replace nsslapd-bakdir=/DOES_NOT_EXIST
Enter password for cn=Directory Manager on ldap://localhost:38901:
Successfully replaced "nsslapd-bakdir"
2. Try to load RHDS instance.
3. Progress bar goes to 100% but instance won't load.
Actual results:
Instance is not loaded.
Expected results:
Instance is loaded.
- clones
-
DIRSRV-382 RHDS Console: instance fails to load when DB backup directory doesn't exist. [dirsrv-12.6]
-
- Closed
-
- links to
-
RHEA-2024:140021
Red Hat Directory Server bug fix and enhancement update