Bug 1269784

Summary:	tools/glusterfind: fix %2F%2F character sequence in file paths emitted in output file
Product:	[Community] GlusterFS	Reporter:	Milind Changire <mchangir>
Component:	glusterfind	Assignee:	Milind Changire <mchangir>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.6	CC:	avishwan, bugs, khiremat
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1269735	Environment:
Last Closed:	2016-03-22 08:19:12 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:	1269735, 1269789
Bug Blocks:

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()