Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1614196

Summary: avc: denied { write } for pid=41998 comm="named" name="named" dev="dm-0" ino=34165723
Product: Red Hat Enterprise Linux 7 Reporter: Ondrej Mejzlik <omejzlik>
Component: bindAssignee: Petr Menšík <pemensik>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: lvrabec, mgrepl, mmalik, pemensik, plautrba, psklenar, ssekidde, thozza, vmojzis
Target Milestone: rcKeywords: Reopened
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: 2019-02-28 13:08:06 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:
Bug Depends On: 1631814    
Bug Blocks:    

Comment 2 Lukas Vrabec 2018-08-10 11:59:56 UTC
Hi, 

You can allow it using:
#semanage boolean -m --on named_write_master_zones

Maybe it needs to be set in postinstall script of bind package.

Comment 3 Petr Sklenar 2018-08-20 06:32:50 UTC
changing component to bind

Comment 4 Petr Menšík 2018-09-20 13:58:42 UTC
This issue seems to be cause by not yet present selinux-policy-targeted package when postscript is executed. See bug #1569466 comment #19 for more details.

Comment 5 Tomáš Hozza 2018-09-21 07:11:06 UTC
(In reply to Lukas Vrabec from comment #2)
> Hi, 
> 
> You can allow it using:
> #semanage boolean -m --on named_write_master_zones
> 
> Maybe it needs to be set in postinstall script of bind package.

For the future, please change the component to proper component and don't close bugs as NOTABUG when it actually IS a bug. This could have been caught much more earlier in BIND than before RC-Snapshot.

Thank you.

Comment 6 Petr Menšík 2019-02-28 13:01:31 UTC
This bug is left open, because selinux-policy boolean macros have some defects. Also, bind should be changed to require only selinux-policy-base in post script. That way, it would always wait until any selinux-policy-{minimal,targeted,mls} is installed. Current macro does not work without them installed but current state requires selinux-policy-targeted to be installed. It depends first on bug #1631814 to be resolved somehow.

Failure can be reproduced, if bind is installed sooner than selinux-policy-targeted. If it is the case, named_write_master_zones is not successfully switched on. Unfortunately it is common case in fresh installation, because bind depends only on selinux-policy, but not selinux-policy-targeted.

Comment 7 Petr Menšík 2019-02-28 13:08:06 UTC
The same issue is better described in bug #1633108. Closing this as duplicate, even it is older.

*** This bug has been marked as a duplicate of bug 1633108 ***