Bug 48834 - Change Behaviour of Upgrade Policies
Change Behaviour of Upgrade Policies
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Policies
UCS 4.3
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
https://help.univention.com/t/explana...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-03-01 14:56 CET by Christian Völker
Modified: 2021-05-14 16:37 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
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?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019021321000255
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 Christian Völker univentionstaff 2019-03-01 14:56:21 CET
With the current Automated update policies we geht behavious as described in https://help.univention.com/t/explanation-automatic-updates-vs-new-releases/8500

So we can upgrade to latest 4.3-x without any issues.

But as soon as we have manually upgraded a single server to the next minor/major (ie 4.4-0) the policy does not update further as the limit is set to 4.3-99.

Changing from 4.3-99 to 4.4-99 allows minor update of all affected servers- no good!

In the end we have to reconfigure the policy or add new policies every time Univention releases a new minor version which st somehow annoying and far away from the idea of "automated updates".

We should reconfigure the "automated update" policy not to tread "Patch Leves" as "Release Updates". 

Then our customers would always be autmatically on the latest patch level available for $MAJOR.$MINOR without the need of manually editing policies after every release.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 16:37:57 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have 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 it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.