-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
sst_idm_ds
-
0
-
False
-
-
None
-
None
-
Bug Fix
Description of a problem
It's not possible to choose DB backend when a new instance is created. And for existing instances WebUI expects `dsconf` to return BDB specific parameters. For example, a page throws an Oops... when I navigate to `Database` tab on an instance with LMDB backend: https://github.com/389ds/389-ds-base/blob/1f95b57fb8b03f72c7d2a2ce5b14eed5ba320407/src/cockpit/389-console/src/database.jsx#L251 ``` Uncaught TypeError: Cannot read properties of undefined (reading '0') at Function.<anonymous> (database.jsx:251:55) at process_queue (cockpit.js:1311:37) at cockpit.js:1324:35 at later_drain (cockpit.js:1205:13) ```
Version-Release number of the selected component
rpm -q 389-ds-base cockpit-389-ds
389-ds-base-2.5.2-2.el9_5.x86_64 cockpit-389-ds-2.5.1-2.module+el9dsrv+22071+e756ccfb.noarch
Browser (if applicable)
Firefox
Steps to reproduce
1. Create a new instance with MDB backend 2. Go to Database tab
Actual results
Observe an Oops...
Expected results
WebUI should support instances with both BDB and LMDB backends and not crash if some attributes are not available.
Additional information
- is cloned by
-
DIRSRV-226 WebUI supports only instances with BDB
- In Progress
- links to
-
RHBA-2024:136844 redhat-ds:12 bug fix update
- mentioned on
(1 mentioned on)