Bug 53701 – Make logrotate maxsize use- and configurable via UCR

Bug 53701 - Make logrotate maxsize use- and configurable via UCR


Summary:	Make logrotate maxsize use- and configurable via UCR

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	logrotate
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-08-24 13:02 CEST by Dirk Schnick
Modified:	2021-08-24 13:02 CEST (History)
CC List:	0 users

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:	2021081921000505
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Schnick

2021-08-24 13:02:42 CEST

In /usr/lib/python2.7/dist-packages/univention/lib/ucrLogrotate.py there is no code that would extract maxsize and the extraction of the ucr vars are hardcoded. If I remember right we are working on generic extraction of given vars?
Anyways I tried to add maxsize 

if configRegistry.get(var + "create"):
			settings["create"] = "create " + configRegistry[var + "create"]
                #added maxsize for testing 
                if configRegistry.get(var + "maxsize"):
                                            settings["maxsize"] = "maxsize " + configRegistry[var + "maxsize"]
	_getBoolDefault("logrotate/missingok", "logrotate/" + name + "/missingok", settings, configRegistry)

and the logrotate configfiles were filled with that option.

I support the customer request in the attached ticket to empower logrotate.