Bug 1358217
Summary: | firewalld errors when writing ifcfg files | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Beniamino Galvani <bgalvani> |
Component: | firewalld | Assignee: | Thomas Woerner <twoerner> |
Status: | CLOSED DUPLICATE | QA Contact: | Tomas Dolezal <todoleza> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | todoleza |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-20 13:50:43 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: | |
Embargoed: |
Description
Beniamino Galvani
2016-07-20 09:53:15 UTC
> But apart from this, what is the reason for firewalld to update ifcfg > files? NetworkManager reads the firewall zone from the ifcfg files and > then calls firewalld D-Bus methods to update the zone, so it seems not > necessary for firewalld to update the connection files. The zone is newly stored only in one place to prevent duplication and configuration errors. Because NetworkManager don't need to be running or there could be an interface which is not NM_CONTROLLED, firewalld needs to write this information on its own. It also uses dbus api to do this. closing as duplicate of already existing selinux bug 1304723 *** This bug has been marked as a duplicate of bug 1304723 *** |