Bug 1006201

Summary:	nagios dependency and hard-coded configuration file locations while icinga can satisfy check-mk dependency
Product:	[Fedora] Fedora EPEL	Reporter:	reader_1000
Component:	check-mk	Assignee:	Andrea Veri <andrea.veri>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	andrea.veri, flatfender
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 14:56:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description reader_1000 2013-09-10 08:31:27 UTC

Description of problem:
Check-mk package installs nagios package as its dependency but icinga (https://www.icinga.org/) package can also satisfy check-mk requirements.
So nagios should be an optional dependency. This may not be a big problem, but since with the way package install itself, config file locations
than needs to bu used for check-mk are hard-coded for nagios package. Check-mk's manual installation lets you to change this locations with  ~/.check_mk_setup.conf file (http://mathias-kettner.com/checkmk_getting_started.html) but I yum installation does not use this file. As a result,
it becomes a lot harder to use check-mk with icinga.

Since there is a ongoing process for icinga package (https://bugzilla.redhat.com/show_bug.cgi?id=693608) it would be nice
to have some way to solve these problems.

Version-Release number of selected component (if applicable):
1.2.2-3

How reproducible:
Always

Steps to Reproduce:
1. yum install check-mk
2.
3.

Actual results:
It installs nagios as dependency and use config files accordingly.

Expected results:
Nagios should be optional and config files should be configured for already installed icinga package.

Additional info:

Comment 1 Andrea Veri 2013-09-10 08:54:07 UTC

We should probably make two seperated packages each with nagios / icinga's configuration files. That way you can 'yum install check-mk-config-nagios' or 'yum install check-mk-config-icinga' accordingly.

I'll look into this. Not top priority right now though since Icinga still has to join the repositories as per https://bugzilla.redhat.com/show_bug.cgi?id=693608.

Comment 2 Matt Pusateri 2015-11-13 16:49:17 UTC

Shinken can also use check-mk or check-km-multisite.

Comment 3 Andrea Veri 2016-02-19 19:58:44 UTC

I should start investigating how to deal with this situation again. It has to be said that according to [1] ~/.check_mk_setup.conf is not honored when setup.sh is ran with the --yes flag, that means I should find another way to support multiple monitoring softwares.

[1] https://mathias-kettner.de/checkmk_calling_setup.html

Comment 4 Ben Cotton 2020-11-05 16:46:54 UTC

This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 5 Ben Cotton 2020-11-30 14:56:58 UTC

EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.