Description of problem: Any change made in "Tuning & Limits" under the "Server Settings" tab is saved in LDAP after the user clicks on the "Save" button but the Console reloads the previous value. The "Reload" icon doesn't trigger any action. Version-Release number of selected component (if applicable): $ cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) $ $ rpm -qa | grep 389-ds 389-ds-base-libs-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.x86_64 cockpit-389-ds-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.noarch 389-ds-base-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.x86_64 $ How reproducible: Always. Steps to Reproduce: 1. Change any parameter and click on the "Save" button. For instance, change the "Number Of Worker Threads" from 16 to 24. The following command is launched to save the changed value in LDAP: CMD: saveConfig: Saving Tuning configuration ==> dsconf -j ldapi://%2fvar%2frun%2fslapd-<INSTANCE>.socket config replace nsslapd-threadnumber=24 2. Check the value: $ sudo dsconf ldapi://%2fvar%2frun%2fslapd-<INSTANCE>.socket config get nsslapd-threadnumber nsslapd-threadnumber: 24 $ 3. The Console still shows the previous value ( 16 ). The reload button doesn't help. Reloading the page shows the new value. Actual results: The previous value is still shown. Expected results: The Console should show the new value. Additional info: Maybe * either implement a reloadConfig() in tuning.jsx as in settings.jsx * or update the state object once the change is successfully done in LDAP.
Replicated the issue as stated above with the following: # rpm -qa | grep 389-ds 389-ds-base-libs-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.x86_64 389-ds-base-devel-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.x86_64 389-ds-base-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.x86_64 389-ds-base-snmp-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.x86_64 cockpit-389-ds-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.noarch 389-ds-base-legacy-tools-1.4.3.13-1.module+el8dsrv+8334+69a46a2e.x86_64 -Launched console and created an instance -Navigated to : Red Hat Directory Server --> Tuning & Limits - Set the value in the "Number Of Worker Threads" from 16 to 24 as stated in the bug - Hit "Save" and nothing happened still shows 16 in the UI. Updated to the fixed version of RHDS rpm -qa | grep 389 389-ds-base-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.x86_64 cockpit-389-ds-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.noarch python3-lib389-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.noarch 389-ds-base-snmp-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.x86_64 389-ds-base-legacy-tools-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.x86_64 linux-firmware-20200619-99.git3890db36.el8.noarch 389-ds-base-libs-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.x86_64 389-ds-base-devel-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.x86_64 Repeated the steps above and the value is updated from 16 --> 24 **NOTE I had to log out of my old session to get the fix to work.
This does not sound like its working correctly. After making the change, the UI should immediately reflect the new value...
(In reply to mreynolds from comment #4) > This does not sound like its working correctly. After making the change, > the UI should immediately reflect the new value... I tested this, and it is working correctly for me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: redhat-ds:11 security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:1243