Bug 797702 - glusterd mountbroker-georeplication.* option is broken
Summary: glusterd mountbroker-georeplication.* option is broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
Assignee: Csaba Henk
QA Contact: Vijaykumar Koppad
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-02-27 03:43 UTC by Csaba Henk
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:22:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: 3.3.0qa45
Embargoed:


Attachments (Terms of Use)

Description Csaba Henk 2012-02-27 03:43:46 UTC
Description of problem:

Specifying an option for glusterd of the format mountbroker-georeplication.*
does not take effect.

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


How reproducible:

Deterministically.

Steps to Reproduce:
1. Set up mountbroker service for geo-replication as discussed in

https://docspace.corp.redhat.com/docs/DOC-93046#for-gluster-slaves-uprivileged-agent
2. Start glusterd with respective volfile.
3. Try to use the mountbroker service with

  gluster system:: mount <user> volfile-server=localhost volfile-id=<volname> client-pid=-1 user-map-root=<user> 'xlator-option=*-dht.assert-no-child-down=true'

(in the example at referred place, <user> is "geonobody" and <volname> is "slavevol").

Actual results:

Error message "2 : failed with this errno (No such file or directory)"

Expected results:

Return with success.

Additional info:

@Venky: issue was already discussed in our Google Chat conversation as of 23rd Jan, please check it.

Comment 1 Anand Avati 2012-03-05 17:17:21 UTC
CHANGE: http://review.gluster.com/2835 (glusterd: mountbroker-geo-replication.* fix) merged in master by Vijay Bellur (vijay)


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