Bug 1115387

Summary:	[Nagios] - When nagios-server-addons rpm is updated, default host and default service comes back.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	nagios-server-addons	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	dpati, nsathyan, rhs-bugs, rhsc-qe-bugs
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.0.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nagios-server-addons-0.1.8-1.el6rhs	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-15 13:49:01 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:

Description RamaKasturi 2014-07-02 09:24:03 UTC

Description of problem:
When nagios server addons rpm is updated, default host i.e temp_node1 and default service PING comes back.

Version-Release number of selected component (if applicable):
nagios-server-addons-0.1.5-1.el6rhs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install nagios-server-addon 0.1.4.2 on RHS node  and start monitoring some hosts.
2. Now update that to 0.1.5-1 by adding right channels and do an yum update.
3. Now restart nagios service by running the command 'service nagios restart'

Actual results:
In the nagios web UI, there comes back the default host 'temp_node1' and default service PING.

Expected results:
Default host and service should not come back.

Additional info:

Comment 1 Ramesh N 2014-07-14 07:31:16 UTC

Upstream patch sent: http://review.gluster.org/8303

Comment 3 RamaKasturi 2014-11-12 10:29:09 UTC

Verified and works fine with build nagios-server-addons-0.1.8-1.el6rhs.noarch.

When nagios-server-addons is updated, temp_node1 and default service PING does not come back.

Comment 5 errata-xmlrpc 2015-01-15 13:49:01 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.

https://rhn.redhat.com/errata/RHBA-2015-0039.html