Bug 1301258 – Rolekit startup brings up firewalld which conflicts with shorewall

Bug 1301258 - Rolekit startup brings up firewalld which conflicts with shorewall

Summary:	Rolekit startup brings up firewalld which conflicts with shorewall

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	rolekit (Show other bugs)
Sub Component:
Version:	23
Hardware:	All Linux

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Thomas Woerner
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-01-23 01:39 EST by Frank Crawford
Modified:	2016-01-25 08:27 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-01-25 08:27:55 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Frank Crawford 2016-01-23 01:39:42 EST

Description of problem:
The latest version of rolekit's systemd configuration file includes a requirement for firewalld.  This conflicts with other firewall products, such as shorewall, and causes incorrect iptable rules to be applied


Version-Release number of selected component (if applicable):
rolekit-0.4.0.1-2.fc23.noarch

How reproducible:
100%

Steps to Reproduce:
1. systemctl disable firewalld.service
2. systemctl stop firewalld.service (if going)
3. systemctl restart rolekit.service

Actual results:
firewalld is restarted

Expected results:
firewalld not running

Additional info:
This appears to only have occurred in the latest RPM.

Comment 1 Stephen Gallagher 2016-01-25 08:27:55 EST

This is intentional. Rolekit has a very tight dependency on firewalld. If you are using shorewall or another firewall service, then you should disable rolekit. The fact that we were missing this explicit dependency previously was a bug; rolekit would not have worked properly without it.

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