While testing negative value for 'search size limit' config option , now a validation error dialog box is shown(not-working.png), earlier it was just a hint down the text box in red colors (working.png)
A error dialog box is shown with validation error. (not-working.png)
error should be part of hint down the text box which was there earlier (working.png)
$ rpm -q freeipa-server freeipa-client ipa-server ipa-client 389-ds-base pki-ca krb5-server [root@dhcp207-43 ~]# rpm -q freeipa-server freeipa-client ipa-server ipa-client 389-ds-base pki-ca krb5-server freeipa-server-4.6.90test-0.fc28.x86_64 freeipa-client-4.6.90test-0.fc28.x86_64 package ipa-server is not installed package ipa-client is not installed 389-ds-base-1.4.0.10-2.fc28.x86_64 pki-ca-10.6.2-1.fc28.noarch krb5-server-1.16.1-7.fc28.x86_64 [root@dhcp207-43 ~]#
This version of freeipa-server i got from PR CI results . http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/25e477ec-78ca-11e8-a040-fa163ed5c549/ http://freeipa-org-pr-ci.s3-website.eu-central-1.amazonaws.com/jobs/25e477ec-78ca-11e8-a040-fa163ed5c549/installed_packages/
Please find the attach images .
This behavior change is linked to commit e8d308196bab1dac5bba7a8a6a517a1e67e877f ipaserver config plugin: Increase search records minimum limit
Where did you get the build? The version number doesn't tell us when the build was created and which commits are in the build. It makes it hard to tell which commit caused the issue.
As @frenaud said, the behavior changed after 59e0c02fbd16135b91f5c1cb1bbf5e1180ad1322, trying to fix #6617, changing the minimum valid value to 10, but accepting -1 or 0.
My guess is that Web UI probably requires the minvalue argument to display the hint, that was removed in favor of a validation function.
minvalue
If we set the minvalue to 10 then will be impossible to set -1 or 0, but if we set the minvalue back to -1 then the alert box will appear for values between 0 and 10, but not for values lower than -1, as expected.
Build info part of the description. Pasting one more time here.
master:
Metadata Update from @cheimes: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
ipa-4-6: