Bug 1719640

Summary: glusterfind command failing with error "%{__python3}: bad interpreter:"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vinayak Papnoi <vpapnoi>
Component: glusterfindAssignee: hari gowtham <hgowtham>
Status: CLOSED ERRATA QA Contact: Vinayak Papnoi <vpapnoi>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: amukherj, hgowtham, kkeithle, rhs-bugs, sheggodu, storage-qa-internal, vdas
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: RHGS 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-6.0-6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-30 12:21:50 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:    
Bug Blocks: 1696809    

Description Vinayak Papnoi 2019-06-12 09:01:03 UTC
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)

Comment 19 Vinayak Papnoi 2019-06-17 06:13:24 UTC
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.

Comment 21 errata-xmlrpc 2019-10-30 12:21:50 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/RHEA-2019:3249