Bug 1986746

Summary:	vsctool.py has wrong interpreter '#!/usr/bin/python2'
Product:	Red Hat Software Collections	Reporter:	Branislav Náter <bnater>
Component:	varnish	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rh-varnish6	CC:	jorton
Target Milestone:	alpha	Keywords:	Reopened
Target Release:	3.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-08 07:28:34 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:

Description Branislav Náter 2021-07-28 09:17:53 UTC

Description of problem:
Shebang test [1] caught this issue [2] in /opt/rh/rh-varnish6/root/usr/share/varnish/vsctool.py:

Shebang has been found in this file:
------------------------------------
/opt/rh/rh-varnish6/root/usr/share/varnish/vsctool.py
(Python script, UTF-8 Unicode text executable)
#!/usr/bin/python2
:: [ 12:25:01 ] :: [   FAIL   ] :: File '/opt/rh/rh-varnish6/root/usr/share/varnish/vsctool.py' has wrong interpreter '#!/usr/bin/python2' 

1. https://wiki.test.redhat.com/SoftwareCollections/GeneralTests#shebangcheck
2. https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2021/07/56378/5637819/10391797/129579738/taskout.log

Version-Release number of selected component (if applicable):
rh-varnish6-varnish-6.0.8-2.el7


Steps to Reproduce:
1. by running test /CoreOS/scl-utils/Sanity/general-shebang-check

Actual results:
failing test

Expected results:
passing test (correct shebang)

Comment 1 Joe Orton 2021-08-03 09:53:27 UTC

Fixed in https://src.osci.redhat.com/rpms/varnish/c/7e5a819bad1a0f9a9b56dda0d579b15048e808be?branch=rhscl-3.7-rh-varnish6-rhel-7 and later

Comment 5 RHEL Program Management 2023-08-08 07:28:34 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.