Bug 33181 - Global limit in revised DNS and DHCP representation feels wrong
Global limit in revised DNS and DHCP representation feels wrong
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Domain management (Generic)
UCS 3.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on: 28248 32381 33205
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-07 11:34 CET by Dirk Wiesenthal
Modified: 2017-08-08 07:10 CEST (History)
5 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): UCS Performance, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2013-11-07 11:34:27 CET
In big environments with more than 2000 DNS entries for a Forward Zone, clicking on that Forward Zone shows the error message "Result yielded more than %(sizelimit) items". The grid does not update, it shows still all zones from the root zone (or something different; it is the last result). This also holds for e.g. Users, when searching for "*name*" (< 2000) and then for "*" (> 2000) but there it did not feel wrong.

With Bug#32381 fixed it is an issue. Either clear the grid or, alternatively, jump back to the last position of the tree (where everything was fine). I would prefer the first one.

+++ This bug was initially created as a clone of Bug #28248 +++

In größeren Umgebungen könnte es hilfreich sein die maximal von LDAP abgefragt Anzahl Objekte global (in der UMC) zu beschränken. So würde eine versehentliche Suche nach allen Benutzer nicht alle Benutzer zurückgeben sondern nur 1000 oder 2000 Objekte.
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:38:56 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Stefan Gohmann univentionstaff 2017-08-08 07:10:47 CEST
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.