Bug 1462753

Summary: glusterfind: syntax error due to uninitialized variable 'end'
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Milind Changire <mchangir>
Component: glusterfindAssignee: Milind Changire <mchangir>
Status: CLOSED ERRATA QA Contact: Anil Shah <ashah>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: amukherj, avishwan, bugs, khiremat, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone: ---   
Target Release: RHGS 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8.4-29 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1462241 Environment:
Last Closed: 2017-09-21 04:59:42 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: 1462241    
Bug Blocks: 1417151    

Comment 2 Atin Mukherjee 2017-06-20 13:11:49 UTC
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/109519/

Comment 5 Anil Shah 2017-06-27 13:29:06 UTC
Earlier was able to hit this issue, after running after glusterfind pre command.

[root@dhcp46-22 ~]# glusterfind  pre backup4  vol0 /tmp/log4.txt
10.70.46.22 - pre failed: Traceback (most recent call last):
   File "/usr/libexec/glusterfs/glusterfind/changelog.py", line 400, in <module>
     if end == -1:
 NameError: name 'end' is not defined
 10.70.46.22 - pre failed: Traceback (most recent call last):
   File "/usr/libexec/glusterfs/glusterfind/changelog.py", line 400, in <module>
     if end == -1:
 NameError: name 'end' is not defined
====================================

[root@rhs-arch-srv1 glusterfind]# glusterfind  pre s1   newvolume /tmp/log4.txt
Generated output file /tmp/log4.txt


Build verified on build glusterfs-3.8.4-31.el7rhgs.x86_64

Comment 7 errata-xmlrpc 2017-09-21 04:59:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774