Bug 1280344

Summary:	Changing users permanently break enabled collections
Product:	Red Hat Software Collections	Reporter:	Josef Stribny <jstribny>
Component:	scl-utils	Assignee:	Joe Orton <jorton>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	hhorak, jorton, kanderso
Target Milestone:	---
Target Release:	3.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:38:21 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 Josef Stribny 2015-11-11 14:21:38 UTC

Description of problem:


Version-Release number of selected component (if applicable):
# rpm -q scl-utils
scl-utils-20130529-17.el7_1.x86_64

Tested on CentOS Linux release 7.1.1503 (Core).

How reproducible:

$ ruby -v
ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
$ scl enable rh-ruby22 bash
$ ruby -v
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]
$ su
Password: 
# echo $X_SCLS
rh-ruby22
# ruby -v
ruby: error while loading shared libraries: libruby.so.2.2: cannot open shared object file: No such file or directory
# scl enable rh-ruby22 bash
# echo $X_SCLS
rh-ruby22
# echo $PATH
/opt/rh/rh-ruby22/root/usr/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/vagrant/.local/bin:/home/vagrant/bin
# echo $LD_LIBRARY_PATH

# ruby -v
ruby: error while loading shared libraries: libruby.so.2.2: cannot open shared object file: No such file or directory


Steps to Reproduce:
1. enable collection
2. change user
3. try to use the collection


Additional info:

It seems that some ENV variables remains when changing users but some not. Because of that enabled collections are broken and enabling them again does not help.

Comment 8 RHEL Program Management 2020-12-15 07:38:21 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.