Bug 1280344 - Changing users permanently break enabled collections
Summary: Changing users permanently break enabled collections
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: scl-utils
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6
Assignee: Joe Orton
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-11 14:21 UTC by Josef Stribny
Modified: 2020-12-15 07:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:38:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.