Bug 1104649 - Dist-geo-rep: In geo-rep mount-broker setup, status shows "Config Corrupted" when status is requested without master and slave url.
Summary: Dist-geo-rep: In geo-rep mount-broker setup, status shows "Config Corrupted" ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard:
Depends On: 1104121
Blocks: 1119739
TreeView+ depends on / blocked
 
Reported: 2014-06-04 12:32 UTC by Avra Sengupta
Modified: 2014-11-11 08:34 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1104121
Environment:
Last Closed: 2014-11-11 08:34:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Anand Avati 2014-06-04 13:35:47 UTC 
REVIEW: http://review.gluster.org/7977 (glusterd/geo-rep: Create the conf file path correctly) posted (#1) for review on master by Avra Sengupta (asengupt)
Comment 2 Anand Avati 2014-06-10 06:28:39 UTC 
REVIEW: http://review.gluster.org/7977 (glusterd/geo-rep: Create the conf file path correctly) posted (#2) for review on master by Avra Sengupta (asengupt)
Comment 3 Anand Avati 2014-06-11 08:53:42 UTC 
REVIEW: http://review.gluster.org/7977 (glusterd/geo-rep: Create the conf file path correctly) posted (#3) for review on master by Avra Sengupta (asengupt)
Comment 4 Anand Avati 2014-06-12 12:49:02 UTC 
COMMIT: http://review.gluster.org/7977 committed in master by Venky Shankar (vshankar) 
------
commit 1f21201a434dd37b621efd3cc5d2ef1fd077c303
Author: Avra Sengupta <asengupt>
Date:   Wed Jun 4 12:30:44 2014 +0000

    glusterd/geo-rep: Create the conf file path correctly
    
    In case of mount brocker, the conf file path needs to
    be correctly created, and then fetch the status file
    
    Change-Id: Iaa1b04ee46f10961a7056e834170d68282c36efa
    BUG: 1104649
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/7977
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kotresh HR <khiremat>
    Reviewed-by: Venky Shankar <vshankar>
    Tested-by: Venky Shankar <vshankar>
Comment 5 Niels de Vos 2014-09-22 12:41:50 UTC 
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/
Comment 6 Niels de Vos 2014-11-11 08:34:04 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users
Note You need to log in before you can comment on or make changes to this bug.