Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 912768 - Packstack needs to add nagios to monitor hosts
Packstack needs to add nagios to monitor hosts
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack (Show other bugs)
2.1
Unspecified Unspecified
high Severity medium
: snapshot4
: 2.1
Assigned To: Martin Magr
Jaroslav Henner
: FutureFeature, Triaged
Depends On: 913063 913064 913065
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-19 10:49 EST by Derek Higgins
Modified: 2016-04-26 12:13 EDT (History)
6 users (show)

See Also:
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 14:24:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0671 normal SHIPPED_LIVE Moderate: openstack-packstack security and bug fix update 2013-03-21 18:22:21 EDT

  None (edit)
Description Derek Higgins 2013-02-19 10:49:55 EST
Packstack needs to install nagios with some basic service monitoring commands for each of the openstack hosts
Comment 5 Derek Higgins 2013-02-25 17:24:56 EST
New Feature merged upstream
https://review.openstack.org/#/c/22521/
Comment 7 Jaroslav Henner 2013-03-06 06:32:49 EST
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 08:39:10 EST
Setting back to on QA, the issue above was caused by conflicting firewall puppet modules
Comment 11 errata-xmlrpc 2013-03-21 14:24:17 EDT
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

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