Bug 969129 - Foreman Installer requires IPTables configuration
Summary: Foreman Installer requires IPTables configuration
Keywords:
Status: CLOSED DUPLICATE of bug 971535
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Installation_and_Configuration_Guide
Version: 3.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: snapshot2
: 3.0
Assignee: Stephen Gordon
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1010310
TreeView+ depends on / blocked
 
Reported: 2013-05-30 17:45 UTC by Jordan OMara
Modified: 2014-11-09 22:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-13 21:28:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jordan OMara 2013-05-30 17:45:09 UTC
The foreman installer currently requires the host to disable iptables to serve Foreman correctly. We need to create and install a suitable IPTables configuration

Comment 1 Charles Crouch 2013-06-03 15:40:43 UTC
We need to document which ports need to be open. No specific iptables configuration should be required for RHOS3.0

Comment 2 Stephen Gordon 2013-06-03 16:11:27 UTC
I will take this, though it's likely the deliverable will be different we don't have the component yet. Also please note that for documentation bugs ECS should be providing the devel_ack+, not engineering.

Comment 3 Stephen Gordon 2013-06-03 16:12:38 UTC
(In reply to Charles Crouch from comment #1)
> We need to document which ports need to be open. No specific iptables
> configuration should be required for RHOS3.0

Just to confirm - based on the movement of this bug - no changes will be made to the packaging and/or installer to ensure that the required firewall rules are created?

Comment 4 Stephen Gordon 2013-06-13 21:28:59 UTC
I can see that Jordan has raised a bug to track the release note for this, so I will close this bug. Tracking bugs for the Foreman documentation deliverable will begin popping up once I have requested the component.

*** This bug has been marked as a duplicate of bug 971535 ***


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