RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1358217 - firewalld errors when writing ifcfg files
Summary: firewalld errors when writing ifcfg files
Keywords:
Status: CLOSED DUPLICATE of bug 1304723
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-20 09:53 UTC by Beniamino Galvani
Modified: 2016-07-20 13:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-20 13:50:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Beniamino Galvani 2016-07-20 09:53:15 UTC 
Description of problem:

On RHEL 7.3 firewalld prints some errors while trying to write to
ifcfg files in /etc/sysconfig/network-scripts/:

firewalld[15502]: ERROR: Failed to open temporary file: [Errno 13] Permission denied: '/etc/sysconfig/network-scripts/ifcfg-connie.TOf4_T'
firewalld[15502]: ERROR: Calling post func <function ifcfg_set_zone_of_interface at 0x7f86276846e0>(('', 'eth6')) failed: [Errno 13] Permission denied: '/etc/sysconfig/network-scripts/ifcfg-connie.TOf4_T'

This is probably caused by the following SELinux denial:

type=SYSCALL msg=audit(1469005938.730:189): arch=c000003e syscall=2 success=no exit=-13 a0=1a1ecc0 a1=200c2 a2=180 a3=67666366692f7374 items=0 ppid=1 pid=15502 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=($
type=AVC msg=audit(1469005938.730:189): avc:  denied  { write } for  pid=15502 comm="firewalld" path="/etc/sysconfig/network-scripts/ifcfg-connie.TOf4_T" dev="dm-0" ino=51616668 scontext=system_u:system_r:firewalld_t:s0 tcontext=system_u$

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.

Except of logs:

05:37:58 NetworkManager[15308]: <debug> [1469007478.9296] device[0x7fbec3ddd320] (eth6): running queued state change to disconnected (id 3812)
05:37:58 NetworkManager[15308]: <info>  [1469007478.9296] device (eth6): state change: deactivating -> disconnected (reason 'new-activation') [110 30 60]
05:37:58 NetworkManager[15308]: <debug> [1469007478.9296] device[0x7fbec3ddd320] (eth6): will enable userland IPv6LL
05:37:58 NetworkManager[15308]: <debug> [1469007478.9297] platform-linux: link: change 8: user-ipv6ll: set IPv6 address generation mode to none
05:37:58 NetworkManager[15308]: <debug> [1469007478.9300] platform-linux: do-request-link: 8
05:37:58 NetworkManager[15308]: <debug> [1469007478.9303] platform-linux: do-change-link[8]: success changing link: success
05:37:58 NetworkManager[15308]: <debug> [1469007478.9307] platform-linux: sysctl: setting '/proc/sys/net/ipv6/conf/eth6/disable_ipv6' to '1' (current value is '0')
05:37:58 NetworkManager[15308]: <debug> [1469007478.9310] platform-linux: sysctl: setting '/proc/sys/net/ipv6/conf/eth6/disable_ipv6' to '0' (current value is '1')
05:37:58 NetworkManager[15308]: <debug> [1469007478.9311] device[0x7fbec3ddd320] (eth6): deactivating device (reason 'new-activation') [60]
05:37:58 NetworkManager[15308]: <debug> [1469007478.9315] firewall: [0x7fbec3e5a0c0,remove:"eth6"]: firewall zone remove eth6:default
05:37:58 NetworkManager[15308]: <debug> [1469007478.9316] device[0x7fbec3ddd320] (eth6): remove_pending_action (3): 'dhcp4' not pending (expected)
05:37:58 NetworkManager[15308]: <debug> [1469007478.9323] kill child process 'dhcp-client-eth6' (16697): waiting up to 500 milliseconds for process to terminate normally after sending SIGTERM (15)...
05:37:58 firewalld[16613]: ERROR: Failed to open temporary file: [Errno 13] Permission denied: '/etc/sysconfig/network-scripts/ifcfg-connie.QdLW36'
05:37:58 firewalld[16613]: ERROR: Calling post func <function ifcfg_set_zone_of_interface at 0x7f1ce1a756e0>(('', 'eth6')) failed: [Errno 13] Permission denied: '/etc/sysconfig/network-scripts/ifcfg-connie.QdLW36'


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

firewalld-0.4.3.2-1.el7.noarch
RHEL 7.3


How reproducible:

The problem is always reproducible in NetworkManager automated tests when a connection specifying a firewall zone is activated/deactivated.
Comment 2 Tomas Dolezal 2016-07-20 13:50:43 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 ***
Note You need to log in before you can comment on or make changes to this bug.