During testing, I set the sizelimit to 1 in WebUI. Afterwards, operations such as viewing user detail or even the IPA Server Configuration fails with the following pop up.
IPA Error 4215: SizeLimitExceeded Configured size limit exceeded
Using the CLI fails with:
ipa: ERROR: Configured size limit exceeded
Once this value is set, it is not possible to change the sizelimit back to a sensible value in WebUI nor in CLI.
I think we should not allow the user to set a sizelimit that can break his IPA instance.
Same behavior happens for sizelimit=2, but not for sizelimit=3. I think we should establish some sensible minimum value and check if the sizelimit the user is trying to set is higher.
I'd be curious to know what entries are being returned in those cases that is causing things to break.
dkupka: I think we've solved something like this before and the problem was in the internal searches for membership or something like that. Not sure though. stn: this might be related to #6383 but would require more thorough investigation. I do not think setting size limit to 1 is sane, though mbasti: this is duplicate of that, close this ticket as a duplicate H: leave the ticket, block #6383 stn: +1 devmtg: no hurry, Future release
Metadata Update from @tkrizek: - Issue assigned to someone - Issue set to the milestone: Future Releases
Metadata Update from @abiagion: - Custom field blocking reset (from #6383) - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1381535 (was: 0) - Issue close_status updated to: None
Metadata Update from @abiagion: - Issue assigned to abiagion (was: someone)
Metadata Update from @rcritten: - Issue set to the milestone: FreeIPA 4.7 (was: Future Releases)
Metadata Update from @rcritten: - Issue set to the milestone: FreeIPA 4.6.5 (was: FreeIPA 4.7)
master:
ipa-4-6:
Metadata Update from @rcritten: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
PR Discussion: https://github.com/freeipa/freeipa/pull/2037
Login to comment on this ticket.