Bug 821443 - log-rotate fails if the goe-rep session is through ssh
log-rotate fails if the goe-rep session is through ssh
Status: CLOSED CURRENTRELEASE
Product: GlusterFS
Classification: Community
Component: geo-replication (Show other bugs)
mainline
x86_64 Linux
medium Severity urgent
: ---
: ---
Assigned To: Venky Shankar
Saurabh
:
Depends On:
Blocks: 817967
  Show dependency treegraph
 
Reported: 2012-05-14 09:52 EDT by Vijaykumar Koppad
Modified: 2016-01-19 01:09 EST (History)
5 users (show)

See Also:
Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-24 13:09:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: 3.3.0qa45
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vijaykumar Koppad 2012-05-14 09:52:10 EDT
Description of problem:If there is geo-rep session between master and slave through ssh, if you do log-rotate. It fails 


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


How reproducible:always 


Steps to Reproduce:
1.start a geo-rep session between master and slave through ssh (master volume can be any type ) 
2.Try geo-rep log-rotate using the command 
gluster volume geo-rep <master> <slave> log-rotate 
  
Actual results: It fails with error 

[root@QA-16 ~]# gluster volume geo vol 172.17.251.56:/root/geo log-rotate
Error rotating log file
geo-replication command failed


Expected results:Log-rotate should succeed 


Additional info:

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