Bug 1269735

Summary: tools/glusterfind: fix %2F%2F character sequence in file paths emitted in output file
Product: [Community] GlusterFS Reporter: Milind Changire <mchangir>
Component: glusterfindAssignee: Milind Changire <mchangir>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: avishwan, khiremat
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-4.1.3 (or higher) Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1269784 1269789 (view as bug list) Environment:
Last Closed: 2018-08-29 03:18:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1269784, 1269789    

Description Milind Changire 2015-10-08 06:41:19 UTC 
Description of problem:
File paths emitted in output file contain %2F%2F as directory separator instead of a single %2F.

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


How reproducible:
Always

Steps to Reproduce:
1. Create glusterfind session on a volume
2. Create files in sub-directories on volume
3. Wait for 20 seconds for changelog rollover
4. Run a glusterfind pre command to generate an output file
5. File will contain paths with %2F%2F character sequence

Actual results:


Expected results:
Only single character sequence of %2F should be present as directory separator

Additional info:
Comment 1 Milind Changire 2015-11-19 06:45:19 UTC 
Fixed in main.py::write_output() of http://review.gluster.org/12362
Comment 2 Milind Changire 2016-02-15 06:51:04 UTC 
Fixed as part of bug 1272006
See comment #1 for patch link
Comment 3 Milind Changire 2016-03-11 08:28:42 UTC 
See comment #1 and comment #2 above
Comment 4 Milind Changire 2016-03-11 08:34:13 UTC 
oops! other bug still in MODIFIED state
will address this later