Bug 1269784 - tools/glusterfind: fix %2F%2F character sequence in file paths emitted in output file
Summary: tools/glusterfind: fix %2F%2F character sequence in file paths emitted in out...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterfind
Version: 3.7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milind Changire
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1269735 1269789
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-08 08:15 UTC by Milind Changire
Modified: 2016-03-22 08:19 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.7.9
Doc Type: Bug Fix
Doc Text:
Clone Of: 1269735
Environment:
Last Closed: 2016-03-22 08:19:12 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Milind Changire 2015-10-08 08:15:48 UTC
+++ This bug was initially created as a clone of Bug #1269735 +++

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 2016-01-05 06:53:52 UTC
fix available with https://code.engineering.redhat.com/gerrit/62252
function tools/glusterfind/src/main.py::write_output()


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