Bug 971584

Summary: PDQ patches incorrectly default "mount_check" option to "False"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Peter Portante <pportant>
Component: gluster-swiftAssignee: Luis Pabón <lpabon>
Status: CLOSED NOTABUG QA Contact: pushpesh sharma <psharma>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0CC: bbandari, kfryklun, madam, rhs-bugs, shaines
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-08 10:22:30 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:

Description Peter Portante 2013-06-06 20:45:25 UTC
The PDQ gluster-swift-plugin RPMs default the account, container and object server "mount_check" option to "false" in the sample configuration files. This can be dangerous, and helpful to new users, where if they don't have the gluster volume properly mounted, their Swift REST API based file creations will possibly occur on the root volume if they are not careful.

This option should default to "true", and the sample configuration file should advise customers to only turn this off after they are confident their volumes are always mounted ahead of the swift *-server processes.

Comment 2 Peter Portante 2013-06-08 10:22:30 UTC
This is not a bug.

For the RHS 2.0 based code, including PDQ, the mount_check option is false to prevent the swift code from doing the mount checking, allowing DiskFile and DiskDir modules to do it. Upstream they are integrated and so this only matters there.