Bug 971584 - PDQ patches incorrectly default "mount_check" option to "False"
Summary: PDQ patches incorrectly default "mount_check" option to "False"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-swift
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Luis Pabón
QA Contact: pushpesh sharma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-06 20:45 UTC by Peter Portante
Modified: 2016-11-08 22:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-08 10:22:30 UTC
Embargoed:


Attachments (Terms of Use)

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.


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