Bug 1371122

Summary:	Disabled firewalld re-enabled after dnf update
Product:	[Fedora] Fedora	Reporter:	dag
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	23	CC:	dag, ecjbosu, twoerner
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-23 13:21:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description dag 2016-08-29 12:01:58 UTC

Description of problem:
When updating a systemd with a disabled firewalld an update will automatically re-enable it

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


How reproducible:
Always

Steps to Reproduce:
1.Run systemctl disable firewalld
2.Run dnf update
3.

Actual results:
Firewall enabled after update

Expected results:
The previous state of disable/enable would be respected

Additional info:

Comment 1 Thomas Woerner 2016-08-29 12:08:07 UTC

Disabling a service with systemctl will only disable the auto-start of the service. If there is someone or something accessing the D-Bus interface of the service or if there is another service asking for the service to be started, then it will be started.

You need to mask a service to make sure that a service is really never started.

Comment 2 dag 2016-08-29 15:32:56 UTC

Ok. That might be the case then. But it had stayed off for quite many reboots before the update...
And sigh for systemd ... Why do we have a "two level" disable?
If I say disable a service I do not want it any more!! - Whatever way it is started...

Comment 3 Joe Byers 2016-12-19 21:15:35 UTC

I am having this problem as well.  Why do we have to disable twice.