+++ 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:
fix available with https://code.engineering.redhat.com/gerrit/62252 function tools/glusterfind/src/main.py::write_output()