Bug 1392538

Summary: The bind and bind-chroot packages specs define and apply group ownership and permissions differently for the /usr/lib64/bind (chroot'd as /var/named/chroot/usr/lib64/bind) directory
Product: [Fedora] Fedora Reporter: Petr Menšík <pemensik>
Component: bindAssignee: Petr Menšík <pemensik>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: akarande, mdshaikh, mruprich, msehnout, mthapa, pemensik, psimerda, psklenar, qe-baseos-daemons, thozza, vonsch, zdohnal
Target Milestone: ---Keywords: Patch
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: bind-9.11.0-2.P1.fc26 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1392531 Environment:
Last Closed: 2016-11-22 16:20:59 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: 1321239    
Bug Blocks:    

Comment 1 Petr Menšík 2016-11-16 15:26:37 UTC 
When bind-chroot is installed, result of

(sudo) rpm -V bind-chroot

is different, when named service is stopped and when is started.

Current version will pass check when stopped.
service named stop
rpm -V bind bind-chroot

But fails after (successful) start
service named start
rpm -V bind bind-chroot

Test case should include both cases.