Bug 1053004

Summary:	Unable to install scl-utils on system with read-only opt directory
Product:	Red Hat Enterprise Linux 6	Reporter:	Marcela Mašláňová <mmaslano>
Component:	scl-utils	Assignee:	Jan Zeleny <jzeleny>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE - Apps <qe-baseos-apps>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	david.jones74, drieden, mmaslano
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1052997	Environment:
Last Closed:	2014-01-15 08:02: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:
Bug Depends On:	1052997
Bug Blocks:

Description Marcela Mašláňová 2014-01-14 14:58:53 UTC

+++ This bug was initially created as a clone of Bug #1052997 +++

Description of problem:
During update or installation, scl-utils attempts to create the directory /opt/rh. In our environment, we mount a read-only NFS export on /opt, so the update fails. 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Attnempt to install or update scl-utils
2.
3.

Actual results:
yum update fails

Expected results:
yum update succeeds, or a clearer error message.

Additional info:
I was trying to update a newly installed system, which apparently had SCL installed by default. It took awhile to figure out why "yum update" was failing, because the error message wasn't very clear on what the problem was: "error: unpacking of archive failed on file /opt/rh: cpio: mkdir". Trying to install manually with rpm, gave more information. 

We're not currently using scl, but it's foreseeable that we could. The main issue here is the system update failing. it would be better if scl didn't try to create /opt/rh during install. Having a package from the standard repo write to /opt is unexpected behavior. It would be better, I think, if scl doesn't create /opt/rh, until it's actually used. After all, scl_prefix is configurable, so it ought to be up to the developer to create the directory where he/she wants it.

From a system admin perspective, it's time consuming for the admin to have to figure out why a system update is failing because of a package he/she isn't using, and may not know what it is. I'm not sure why SCL is installed on our systems. It may have come in with "Developer Tools."