Bug 28804 - Cache Verhalten PKGDB Modul
Cache Verhalten PKGDB Modul
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC - Software monitor
UCS 3.0
Other Linux
: P5 normal (vote)
: UCS 3.2
Assigned To: Florian Best
Moritz Muehlenhoff
: interim-1
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-17 09:50 CEST by Stefan Gohmann
Modified: 2013-11-19 06:44 CET (History)
2 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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2012-10-17 09:50:28 CEST
Wenn ein neuer Rechner zur PKGDB hinzugefügt wurde, dann findet eine Suche den Rechner erst, wenn man sich neu an UMC anmeldet.
Comment 1 Florian Best univentionstaff 2013-07-02 12:32:24 CEST
The caching mechanism is a workaround (to not querying the sql database again when sorting the Grid columns) and will be removed at Bug #30967.

*** This bug has been marked as a duplicate of bug 30967 ***
Comment 2 Florian Best univentionstaff 2013-07-02 12:34:21 CEST
> *** This bug has been marked as a duplicate of bug 30967 ***
Not as duplicate.
Comment 3 Florian Best univentionstaff 2013-07-04 10:48:39 CEST
The caching mechanism has been removed.
Comment 4 Moritz Muehlenhoff univentionstaff 2013-08-14 10:06:40 CEST
A new member server which was joined into the domain is now directly shown in the systems search menu without requiring a re-login. I've amemded the changelog a bit, otherwise ok.
Comment 5 Stefan Gohmann univentionstaff 2013-11-19 06:44:09 CET
UCS 3.2 has been released:
 http://docs.univention.de/release-notes-3.2-en.html
 http://docs.univention.de/release-notes-3.2-de.html

If this error occurs again, please use "Clone This Bug".