Bug 754147

Summary:	shorewall fails to start
Product:	[Fedora] Fedora	Reporter:	Nerijus Baliūnas <nerijus>
Component:	shorewall	Assignee:	Jonathan Underwood <jonathan.underwood>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	jonathan.underwood
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-15 15:06:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Nerijus Baliūnas 2011-11-15 14:18:05 UTC

After systemctl start shorewall.service I see in syslog:

shorewall.service has an ExecReload setting, which is not allowed for Type=oneshot services. Refusing.

It starts after I comment out "Type=oneshot" in /lib/systemd/system/shorewall.service.

But now shorewall does not start at boot:
ERROR: Can't determine the IP address of eth2: Firewall state not changed

Is it possible to start shorewall only after /etc/rc.d/init.d/network starts?

Comment 1 Nerijus Baliūnas 2011-11-15 15:06:34 UTC

Changing the line
After=syslog.target
to
After=syslog.target network.target
helped. But I see this is done in 4.4.23.3-6.fc16 already in updates-testing.
Should probably be pushed to updates until more reports start to come.