Bug 1191817 - [Doc] iptables must be installed on RHEL7
Summary: [Doc] iptables must be installed on RHEL7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Deploying_OpenStack_Learning_Environments
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ga
: 7.0 (Kilo)
Assignee: Martin Lopes
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1199866
TreeView+ depends on / blocked
 
Reported: 2015-02-12 03:44 UTC by Summer Long
Modified: 2015-08-03 17:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-17 02:07:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Summer Long 2015-02-12 03:44:02 UTC
Description of problem:
RHEL7 doesn't automatically have iptables installed (normally uses NetworkManager), but the deploy guide starts off with 'update the iptable' in
2.3.2. Configure the Firewall to Allow Database Traffic


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

Comment 3 Summer Long 2015-02-12 04:06:22 UTC
Also, 'service iptables restart' should be changed to 'systemctl restart iptables.service'

Comment 4 Andrew Dahms 2015-03-08 23:21:13 UTC
Assigning to Martin for review.

Comment 7 Summer Long 2015-03-09 06:33:50 UTC
Yup, installed, however /etc/sysconfig/iptables file doesn't exist yet. If starting from scratch, perhaps should have initial demo file? Tried putting just the one line in, and it doesn't start up. Also, shouldn't be 'restart', but 'start'.

Comment 8 Martin Lopes 2015-03-10 06:31:55 UTC
Yes, I think it would be better to add a "# yum install iptables-services" to the "Disable firewalld" section, since it's clear not all systems are going to have it installed.

Working on getting that in.

Comment 10 Martin Lopes 2015-03-17 00:40:15 UTC
Successfully tested steps with iptables-services installed.

Comment 11 Summer Long 2015-03-17 01:20:12 UTC
Verified.


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