Bug 912768

Summary: Packstack needs to add nagios to monitor hosts
Product: Red Hat OpenStack Reporter: Derek Higgins <derekh>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED ERRATA QA Contact: Jaroslav Henner <jhenner>
Severity: medium Docs Contact:
Priority: high    
Version: 2.1CC: aortega, apevec, derekh, jhenner, lhh, ykaul
Target Milestone: snapshot4Keywords: FutureFeature, Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-packstack-2012.2.3-0.1.dev454 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-21 18:24:17 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:
Embargoed:
Bug Depends On: 913063, 913064, 913065    
Bug Blocks:    

Description Derek Higgins 2013-02-19 15:49:55 UTC 
Packstack needs to install nagios with some basic service monitoring commands for each of the openstack hosts
Comment 5 Derek Higgins 2013-02-25 22:24:56 UTC 
New Feature merged upstream
https://review.openstack.org/#/c/22521/
Comment 7 Jaroslav Henner 2013-03-06 11:32:49 UTC 
Nagios is working, but it reports:

Service Critical[03-06-2013 10:05:56] SERVICE ALERT: 10.34.69.2;5 minute load average;CRITICAL;HARD;3;Connection refused or timed out
Service Notification[03-06-2013 10:05:16] SERVICE NOTIFICATION: nagiosadmin;10.34.69.3;Percent disk space used on /var;CRITICAL;notify-service-by-email;Connection refused or timed out
Service Critical[03-06-2013 10:05:16] SERVICE ALERT: 10.34.69.3;Percent disk space used on /var;CRITICAL;HARD;3;Connection refused or timed out
...

I am using controller + 2 nodes
Comment 8 Derek Higgins 2013-03-06 13:39:10 UTC 
Setting back to on QA, the issue above was caused by conflicting firewall puppet modules
Comment 11 errata-xmlrpc 2013-03-21 18:24:17 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/RHSA-2013-0671.html