Bug 1371122 - Disabled firewalld re-enabled after dnf update
Summary: Disabled firewalld re-enabled after dnf update
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: firewalld
Version: 23
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 12:01 UTC by dag
Modified: 2016-12-19 21:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-23 13:21:53 UTC
Type: Bug


Attachments (Terms of Use)

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.


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