-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebUI supports only instances with BDB #6065
Labels
lmdb
LMDB related
Comments
vashirov
added
lmdb
LMDB related
needs triage
The issue will be triaged during scrum
labels
Feb 1, 2024
Created IDMDS-4185 ticket |
jchapma
added a commit
to jchapma/389-ds-base
that referenced
this issue
Aug 14, 2024
Description: BDB specific attributes are not supported by the web console, resulting in an "Ooops" when the Database tab is selected. Fix Description: Add a new global Database configuration element for MDB layout. Add support to detect what DB engine is configured, and display the correct layout on rendering. Relates: 389ds#6065 Reviewed by:
droideck
pushed a commit
to jchapma/389-ds-base
that referenced
this issue
Aug 20, 2024
Description: BDB specific attributes are not supported by the web console, resulting in an "Ooops" when the Database tab is selected. Fix Description: Add a new global Database configuration element for MDB layout. Add support to detect what DB engine is configured, and display the correct layout on rendering. Relates: 389ds#6065 Reviewed by:
jchapma
added a commit
to jchapma/389-ds-base
that referenced
this issue
Sep 19, 2024
Description: BDB specific attributes are not supported by the web console, resulting in an "Ooops" when the Database tab is selected. Fix Description: Add a new global Database configuration element for MDB layout. Add support to detect what DB engine is configured, and display the correct layout on rendering. Relates: 389ds#6065 Reviewed by:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
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 toDatabase
tab on an instance with LMDB backend:389-ds-base/src/cockpit/389-console/src/database.jsx
Line 251 in 1f95b57
Package Version and Platform:
Steps to Reproduce
Steps to reproduce the behavior:
Expected results
WebUI should support instances with both BDB and LMDB backends and not crash if some attributes are not available.
The text was updated successfully, but these errors were encountered: