Bug 52275 - Wrong chmod set for UVMM cron and logrotate conf files
Wrong chmod set for UVMM cron and logrotate conf files
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Virtualization - UVMM
UCS 4.4
amd64 All
: P5 major (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-10-28 13:22 CET by andipilz
Modified: 2023-06-28 10:46 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 4: Will affect most installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.229
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 andipilz 2020-10-28 13:22:18 CET
When UVMM is installed, the following error messages are given:

a) by Email to Admin:

   /etc/cron.daily/logrotate:
   error: Ignoring univention-virtual-machine-manager-daemon because of bad file mode - must be 0644 or 0444.

and b) by entry in syslog

   (*system*univention-virtual-machine-manager-daemon) INSECURE MODE (group/other writable) (/etc/cron.d/univention-virtual-machine-manager-daemon)

Correct setting via chmod works temporarily, but after less than 2 days both are reset to the wrong modes.

Result is, cron-jobs and log rotate do not work correctly.
Comment 1 Philipp Hahn univentionstaff 2023-06-28 10:44:08 CEST
UVMM and virtualization with UCS is deprecated and will no longer be developed in UCS 4.4; they have already been removed from UCS 5.0.