Bug 910188 - swift checks for mount points which are alphanumeric and gluster uses ones with dashes
Summary: swift checks for mount points which are alphanumeric and gluster uses ones wi...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: object-storage
Version: 3.3.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Thiago da Silva
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-12 00:07 UTC by Paul Smith
Modified: 2014-12-14 19:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-14 19:40:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Paul Smith 2013-02-12 00:07:54 UTC
Description of problem: Gluster UFO uses swifts check.mount. Swift's check mount checks for an alpha numeric string which fails if the mount point has a '-' in the name. 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 crisbud@redhat.com 2014-01-27 11:26:36 UTC
It would be great if steps to reproduce are provided. 

Current latest icehouse based gluster-swift code using 

devices = /mnt/gluster-object in object-server.conf file where it mounts the gluster volumes. There are now failures reported with this mount point name having '-' in it. 

So this is "Not a Bug ". 


I thought to assign it back to Paul. Adding QA contact.

Comment 3 pushpesh sharma 2014-01-27 12:02:30 UTC
I feel the BZ was about auto-mount check feature we had in earlier version of gluster-swift.As there is no auto mount check in the current upstream version of gluster-swift, and there is no problem so far observed with any hostname family, I am marking this as verified. Open a new BZ with steps to reproduce if problem persist.

Comment 6 Niels de Vos 2014-11-27 14:54:08 UTC
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.


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