Bug 1318780 - Firewalld down after launch-fusor-installer
Summary: Firewalld down after launch-fusor-installer
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: fusor-installer
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: TP3
: 1.0
Assignee: Jason Montleon
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: rhci-sprint-14
TreeView+ depends on / blocked
 
Reported: 2016-03-17 19:15 UTC by Thom Carlin
Modified: 2016-04-29 16:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-21 15:52:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Thom Carlin 2016-03-17 19:15:38 UTC
Description of problem:

After launch-fusor-installer finishes, firewalld service is down.  It should be up.

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

TP3_RC1

How reproducible:

100%

Steps to Reproduce:
1. Install RHCI ISO
2. Log in to run launch-fusor-installer
3. service firewalld status

Actual results:

Active: inactive (dead)
[...]
Stopped firewalld

Expected results:

Active: active (running)
[...]
Started firewalld

Additional info:

iptables is running

Workaround: systemctl start firewalld

Comment 1 Jason Montleon 2016-03-21 15:52:38 UTC
we purposefully stop firewalld and start iptables. To date we haven't found or written a puppet module capable of properly managing firewalld.

systemctl status iptables
● iptables.service - IPv4 firewall with iptables
   Loaded: loaded (/usr/lib/systemd/system/iptables.service; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2016-03-21 11:19:24 EDT; 32min ago
  Process: 20378 ExecStop=/usr/libexec/iptables/iptables.init stop (code=exited, status=0/SUCCESS)
  Process: 20454 ExecStart=/usr/libexec/iptables/iptables.init start (code=exited, status=0/SUCCESS)
 Main PID: 20454 (code=exited, status=0/SUCCESS)

Mar 21 11:19:24 qci.example.com systemd[1]: Starting IPv4 firewall with iptables...
Mar 21 11:19:24 qci.example.com iptables.init[20454]: iptables: Applying firewall rules: [  OK  ]
Mar 21 11:19:24 qci.example.com systemd[1]: Started IPv4 firewall with iptables.

Comment 2 Thom Carlin 2016-03-21 16:11:32 UTC
Is this true also for TripleO?

Comment 3 Jason Montleon 2016-03-21 16:29:33 UTC
The OOO iso firewall configuration is handled by the OOO teams installer. I would imagine, based on output I have seen from their installer that the same is true.


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