Bug 988906 - Dist-geo-rep : 'gluster volume geo <mater_vol> <slave_ip>::<slvae_vol> config' showing wrong gluster_log_file
Summary: Dist-geo-rep : 'gluster volume geo <mater_vol> <slave_ip>::<slvae_vol> config...
Keywords:
Status: CLOSED DUPLICATE of bug 984582
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: 2.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Venky Shankar
QA Contact: amainkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-26 16:37 UTC by Rachana Patel
Modified: 2015-04-20 11:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-29 07:26:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Rachana Patel 2013-07-26 16:37:31 UTC
Description of problem:
 Dist-geo-rep : 'gluster volume geo <mater_vol> <slave_ip>::<slvae_vol> config'  showing wrong gluster_log_file

Version-Release number of selected component (if applicable):
3.4.0.12rhs.beta6-1.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
[root@DVM2 ~]# gluster volume geo test5 rhsauto018.lab.eng.blr.redhat.com::slave5  config | grep log_file
log_file: /var/log/glusterfs/geo-replication/test5/ssh%3A%2F%2Froot%4010.70.36.248%3Agluster%3A%2F%2F127.0.0.1%3Aslave5.log
gluster_log_file: /var/log/glusterfs/geo-replication/test5/ssh%3A%2F%2Froot%4010.70.36.248%3Agluster%3A%2F%2F127.0.0.1%3Aslave5.gluster.log   <--

[root@DVM2 ~]# ls -l /var/log/glusterfs/geo-replication/test5
total 92
-rw-------. 1 root root 25233 Jul 26 06:24 ssh%3A%2F%2Froot%4010.70.36.248%3Agluster%3A%2F%2F127.0.0.1%3Aslave5.%2Frhs%2Fbrick5.gluster.log     <-----
-rw-r--r--. 1 root root 57720 Jul 26 14:06 ssh%3A%2F%2Froot%4010.70.36.248%3Agluster%3A%2F%2F127.0.0.1%3Aslave5.log

Expected results:


Additional info:

Comment 2 Avra Sengupta 2013-07-29 07:26:48 UTC

*** This bug has been marked as a duplicate of bug 984582 ***


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