Bug 726105 - [vdsm] No check for group permissions during creation of file data domain
Summary: [vdsm] No check for group permissions during creation of file data domain
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: x86_64
OS: Linux
urgent
medium
Target Milestone: beta
: ---
Assignee: Saggi Mizrahi
QA Contact: Jakub Libosvar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 14:40 UTC by Jakub Libosvar
Modified: 2011-12-06 07:33 UTC (History)
6 users (show)

Fixed In Version: vdsm-4.9-96.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 07:33:57 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

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


Note You need to log in before you can comment on or make changes to this bug.