Bug 33192 - No reload of UCR variables in some UMC modules
No reload of UCR variables in some UMC modules
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 3.2
Other Linux
: P3 normal (vote)
: UCS 3.2-x
Assigned To: UMC maintainers
:
Depends on: 31752
Blocks: 30811
  Show dependency treegraph
 
Reported: 2013-11-07 13:11 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):
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 13:11:53 CET
The comment below has not been taken into account. At least UDM now has issues because it does not reload the max sizelimit (it relied on that global instance to do it automatically). So after getting the error message: "Too many results. Change the following UCR variable" and changing the following UCR variable, the user gets the very same message again.

At least
ack-grep "import.*ucr"

There could be more critical situations (did not check)

+++ This bug was initially created as a clone of Bug #31752 comment 5 +++

(In reply to Florian Best from comment #5)
> univention.management.console.config provides a global UCR instance (the
> instance which is realoaded automatically). This is used and relies on it in
> various (at least 3) places of the UMC-Server.
Comment 1 Dirk Wiesenthal univentionstaff 2013-11-07 14:47:17 CET
This is a generic UMC bug which can be seen in UDM (and maybe elsewhere).

ack-grep "import.*ucr"

The code of old UMC modules was not adapted during the cloned bug. In UDM it may not be critical, but maybe in another module? I do not know yet.
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:40:17 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 3 Stefan Gohmann univentionstaff 2017-08-08 07:10:50 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.