Description of problem: ----------------------- After upgrading to the RHGS 3.5.0 interim builds (glusterfs-6.0-5.el7rhgs.x86_64) from 'glusterfs-6.0-3.el7rhgs.x86_64' the glusterfind command is failing with the following error message: # glusterfind -bash: /usr/bin/glusterfind: %{__python3}: bad interpreter: No such file or directory # glusterfind list -bash: /usr/bin/glusterfind: %{__python3}: bad interpreter: No such file or directory # glusterfind create --help -bash: /usr/bin/glusterfind: %{__python3}: bad interpreter: No such file or directory Version-Release number of selected component (if applicable): ------------------------------------------------------------- glusterfs-6.0-5.el7rhgs.x86_64 How reproducible: ----------------- 2/2 Steps to Reproduce: ------------------- 1. Install RHGS 3.5.0 interim builds (glusterfs-6.0-5.el7rhgs.x86_64) 2. Perform any glusterfind command Actual results: --------------- Same as in description. Expected results: ----------------- Glusterfind commands should be successful (or unsuccessful with appropriate error message) Additional info: ---------------- The functionality was working fine until the previous interim build (glusterfs-6.0-3.el7rhgs.x86_64)
Build version: glusterfs-6.0-6.el7rhgs.x86_64 With the above mentioned builds, the glusterfind commands are running as expected without the error mentioned in the description. # glusterfind usage: glusterfind [-h] {create,delete,list,pre,query,post} ... glusterfind: error: too few arguments # glusterfind create usage: glusterfind create [-h] [--debug] [--force] [--reset-session-time] session volume glusterfind create: error: too few arguments # glusterfind list No sessions found. # glusterfind create testsess alpha Session testsess created with volume alpha # glusterfind list SESSION VOLUME SESSION TIME --------------------------------------------------------------------------- testsess alpha 2019-06-17 11:41:39 # glusterfind create --help usage: glusterfind create [-h] [--debug] [--force] [--reset-session-time] session volume positional arguments: session Session Name volume Volume Name optional arguments: -h, --help show this help message and exit --debug Debug --force Force option to recreate the session --reset-session-time Reset Session Time to Current Time Hence, moving the bug to VERIFIED.
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/RHEA-2019:3249