Bug 1027835 - Dist-geo-rep : geo-rep status detail fail to count for files skipped due to presence of file with the same name on slave.
Dist-geo-rep : geo-rep status detail fail to count for files skipped due to p...
Status: CLOSED EOL
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: geo-replication (Show other bugs)
2.1
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
storage-qa-internal@redhat.com
status
: ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-07 07:58 EST by Vijaykumar Koppad
Modified: 2015-11-25 03:51 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Vijaykumar Koppad 2013-11-07 07:58:48 EST
Description of problem: geo-rep status detail fail to count for files skipped due to presence of the same  file on slave.


Version-Release number of selected component (if applicable):
glusterfs-3.4.0.39rhs-1

How reproducible:Happens everytime.


Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave.
2.create a file on slave with name "file"
3.create a file with the same name on master.
4.Now do echo "fefe" > file on master 
5. check the status detail

Actual results: geo-rep won't increment for files skipped, but actually increment for files synced 


Expected results: It should actually increment for the files skipped. 


Additional info:
Comment 3 Aravinda VK 2015-11-25 03:50:29 EST
Closing this bug since RHGS 2.1 release reached EOL. Required bugs are cloned to RHGS 3.1. Please re-open this issue if found again.
Comment 4 Aravinda VK 2015-11-25 03:51:52 EST
Closing this bug since RHGS 2.1 release reached EOL. Required bugs are cloned to RHGS 3.1. Please re-open this issue if found again.

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