Bug 50112 - Missing UCR header: /etc/nagios-plugins/config/univention-{samba,s4-connector}.cfg
Summary: Missing UCR header: /etc/nagios-plugins/config/univention-{samba,s4-connector...
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Monitoring (Prometheus or Nagios)
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 50109
Blocks:
  Show dependency treegraph
 
Reported: 2019-09-05 13:04 CEST by Philipp Hahn
Modified: 2024-06-27 12:10 CEST (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
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):
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2019-09-05 13:04:18 CEST
+++ This bug was initially created as a clone of Bug #50109 +++
test/ucs-test/tests/03_ucr/63checkucrwarning:
  Error: Missing UCR header for /etc/nagios-plugins/config/univention-samba.cfg
  Error: Missing UCR header for /etc/nagios-plugins/config/univention-s4-connector.cfg

# dpkg -S /etc/univention/templates/files/etc/nagios-plugins/config/univention-s*.cfg
univention-nagios-s4-connector: /etc/univention/templates/files/etc/nagios-plugins/config/univention-s4-connector.cfg
univention-nagios-samba: /etc/univention/templates/files/etc/nagios-plugins/config/univention-samba.cfg

Patch: +@%@UCRWARNING=# @%@

Please remove the file from WHITELIST in the ucs-test after fixing.
Comment 1 Jan-Luca Kiok univentionstaff 2024-06-27 12:10:02 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.