Bug 1318343 - The firewall rule for Nagios is not correct,
Summary: The firewall rule for Nagios is not correct,
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: 8.0 (Liberty)
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-16 15:11 UTC by Hitesh ingole
Modified: 2016-12-05 01:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-05 01:57:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Hitesh ingole 2016-03-16 15:11:54 UTC
Description of problem:
The firewall rule in the below link under "⁠13.2.3. Configure NRPE" differs  from description.

~~~~
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/5/html/Installation_and_Configuration_Guide/sect-Configure_Nagios.html
~~~

The description points the port should be open for UDP but the rule is gove n for tcp so there is a difference between the description and example.
~~~~

    Add an INPUT rule allowing UDP traffic on port 5666 to this file. The new rule must appear before any INPUT rules that REJECT traffic.

    -A INPUT -p tcp --dport 5666 -j ACCEPT

    Save the changes to the /etc/sysconfig/iptables file.
    Restart the iptables service for the firewall changes to take effect.

    # service iptables restart

For Red Hat Enterprise Linux 7-based systems, run the following commands:

# firewall-cmd --permanent --add-port=5666/udp
# firewall-cmd --add-port=5666/udp
~~~

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
The example and the description does not match.


Expected results:
The description of rule should match.
Either it should be tcp or UDP

Additional info:
In a case customer reported that the NRPE was using tcp.

Comment 3 Lucy Bopf 2016-12-05 01:57:43 UTC
This bug exists only in the OSP 5 documentation, and has been fixed or removed in subsequent versions.

Closing.


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