Bug 726105

Summary: [vdsm] No check for group permissions during creation of file data domain
Product: Red Hat Enterprise Linux 6 Reporter: Jakub Libosvar <jlibosva>
Component: vdsmAssignee: Saggi Mizrahi <smizrahi>
Status: CLOSED ERRATA QA Contact: Jakub Libosvar <jlibosva>
Severity: medium Docs Contact:
Priority: urgent    
Version: 6.1CC: abaron, bazulay, danken, iheim, ilvovsky, ykaul
Target Milestone: beta   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.9-96.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 07:33:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jakub Libosvar 2011-07-27 14:40:35 UTC 
Description of problem:
If there badly set permissions (700 - no kvm permissions) on directory from which administrator wants to create data domain, creation succeeds but fails when attempting to start VM that has image on mentioned domain. vdsm correctly prints messages about wrong permissions on image during start. I think it would be good to prevent such a situation by checking permissions during domain creation for groups as well.

Version-Release number of selected component (if applicable):
vdsm-4.9-84.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create local (or nfs) data-center
2. Make a directory (e.g. /mnt/local)
3. chown 36:36 /mnt/local; chmod 700 /mnt/local
4. Create data domain from this directory
  
Actual results:
Domain is created successfully

Expected results:
There is check that detects wrong permissions on the directory
Comment 1 Saggi Mizrahi 2011-08-02 12:50:40 UTC 
http://gerrit.usersys.redhat.com/#change,776
Comment 2 Jakub Libosvar 2011-09-01 06:54:52 UTC 
Verified vdsm-96
Comment 3 errata-xmlrpc 2011-12-06 07:33:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html