Bug 1096154 - Nagios installation fails
Summary: Nagios installation fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 5.0 (RHEL 7)
Assignee: Lukas Bezdicka
QA Contact: Ido Ovadia
URL:
Whiteboard:
Depends On:
Blocks: 1101665
TreeView+ depends on / blocked
 
Reported: 2014-05-09 10:08 UTC by Attila Fazekas
Modified: 2014-09-08 05:43 UTC (History)
7 users (show)

Fixed In Version: openstack-packstack-2014.1.1-0.15.dev1068.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, PackStack would fail under certain circumstances when attempting to install Nagios. This was caused by PackStack attempting to install the nagios-plugins-nrpe package, which was not present in the OpenStack repositories, resulting in a fatal error. Now, the logic used to install this package has been revised so that PackStack will attempt to install the nagios-plugins-nrpe package if that package is available, or install the monitoring-plugins-nrpe package if the nagios-plugins-nrpe package is not available, allowing PackStack to install Nagios successfully.
Clone Of:
: 1101665 (view as bug list)
Environment:
Last Closed: 2014-07-08 15:38:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 97267 0 None None None Never
Red Hat Product Errata RHEA-2014:0846 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement - Packstack 2014-07-08 19:23:14 UTC

Description Attila Fazekas 2014-05-09 10:08:08 UTC
Description of problem:
Nagios nrpe plugin installation fails.

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

nagios-3.5.1-4.el7.x86_64
nagios-common-3.5.1-4.el7.x86_64
openstack-packstack-puppet-2014.1.1-0.11.1.dev1055.el7ost.noarch
openstack-packstack-2014.1.1-0.11.1.dev1055.el7ost.noarch

How reproducible:
always

Steps to Reproduce:
1. Add CONFIG_NAGIOS_INSTALL=y to the packstack answer file
2. packstack --answer-file=my-answer-file

Actual results:
The puppet install step fails with:
ERROR : Error appeared during Puppet run: 172.16.0.15_nagios.pp
Package nagios-plugins-nrpe has not been found in enabled Yum repos.
You will find full trace in log /var/tmp/packstack/20140509-095743-Bzy1CO/manifests/172.16.0.15_nagios.pp.log
Please check log file /var/tmp/packstack/20140509-095743-Bzy1CO/openstack-setup.log for more information

Details:

Info: Class[Apache::Service]: Scheduling refresh of Service[httpd]
Debug: /Stage[main]/Apache/Apache::Vhost[default-ssl]/File[15-default-ssl.conf]: Nothing to manage: no ensure and the resource doesn't exist
Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Package[nagios-plugins-nrpe] has failures: true
Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Package[nagios-plugins-ping] has failures: true
Warning: /Stage[main]/Apache::Service/Service[httpd]: Skipping because of failed dependencies

Expected results:
It Installs the nagios packages from the openstack repository.

Additional info:
'nagios-plugins-nrpe' package is not in the openstack repo, but 'monitoring-plugins-nrpe' is.

Comment 2 Lon Hohberger 2014-05-27 17:39:14 UTC
Disabling the present 'disable-nagios.patch' and replacing it with the following grants us a working nagios installation on RHOS 5 for RHEL 7:

https://bugzilla.redhat.com/attachment.cgi?id=899582&action=diff

Comment 5 Ido Ovadia 2014-06-08 11:56:27 UTC
Verified
========

nagios-3.5.1-4.el7.x86_64
openstack-packstack-2014.1.1-0.22.dev1117.el7ost.noarch

Comment 9 errata-xmlrpc 2014-07-08 15:38:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0846.html


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