Bug 1800482 - check_icmp: Multiple hosts not working
Summary: check_icmp: Multiple hosts not working
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: nagios-plugins
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Guido Aulisi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-07 08:19 UTC by Alexander Lex
Modified: 2024-07-09 03:02 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 03:02:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alexander Lex 2020-02-07 08:19:43 UTC
Description of problem:
There are two hostnames configured with min_hosts_alive set to 1. One host is down (passive cluster node) and one is up. Check result changed from OK to CRITICAL with no changes in host state. I would except it to still return Ok.

Version-Release number of selected component (if applicable):
nagios-plugins-icmp-2.3.1-1.el7.x86_64

How reproducible:
Execute check_icmp with two host addresses and set the min_hosts_alive to 1. If one node is in down state, check is changing to CRITICAL.

/usr/lib64/nagios/plugins/check_icmp -H ip_of_node_down ip_of_node_up -m 1

Actual results:
CRITICAL State

Expected results:
OK State

Additional info:
Github Issue
https://github.com/nagios-plugins/nagios-plugins/issues/520

Pull Request was also created.

Comment 1 Fedora Admin XMLRPC Client 2020-02-25 16:34:58 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 2 Fedora Admin user for bugzilla script actions 2021-02-20 00:05:40 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 3 Troy Dawson 2024-07-09 03:02:14 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.


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