Bug 1277082 - Rebase of nsca packages in RHEL 6
Rebase of nsca packages in RHEL 6
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: nagios-server-addons (Show other bugs)
3.1
Unspecified Unspecified
high Severity medium
: ---
: RHGS 3.1.2
Assigned To: Ramesh N
Triveni Rao
: Rebase, ZStream
Depends On:
Blocks: 1258718 1260783
  Show dependency treegraph
 
Reported: 2015-11-02 04:49 EST by Sahina Bose
Modified: 2016-05-16 00:39 EDT (History)
6 users (show)

See Also:
Fixed In Version: nsca-2.9.1-4.1.el6rhs
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-03-01 01:12:36 EST
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)

  None (edit)
Description Sahina Bose 2015-11-02 04:49:16 EST
Description of problem:

nsca packages shipped in RHEL 6 for Gluster nodes and Gluster storage console needs to be rebased to 2.9.1 version. This is needed to solve the compatibility issues faced with older nsca servers and newer clients

Version-Release number of selected component (if applicable):
3.1 (nsca-2.7.2 - currently available)

How reproducible:
NA
Comment 3 Ramesh N 2015-11-03 06:45:05 EST
Re-based the nsca package with nsca-2.9.1. This should fix the version/pocket size mismatch issue reported in rhbz#1258718.
Comment 5 Triveni Rao 2015-11-20 05:59:48 EST
Bug is verified and updated the same in another bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1258718
Comment 6 Triveni Rao 2015-11-24 06:32:26 EST
nsca notifications were seen properly on the nagios UI but Cluster quorum status showed quorum lost message initially and then started flapping between the states after some time.

I have raised a separate bug for this issue.

https://bugzilla.redhat.com/show_bug.cgi?id=1284874
Comment 9 errata-xmlrpc 2016-03-01 01:12:36 EST
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-2016-0310.html

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