Bug 752233

Summary:	rh-amazon-rhui-client creates /etc/sysconfig/rh-cloud-firstboot with incorrect selinux file context
Product:	Red Hat Enterprise Linux 6	Reporter:	Brett Lentz <blentz>
Component:	ec2-images	Assignee:	John Matthews <jmatthew>
Status:	CLOSED WONTFIX	QA Contact:	Vratislav Hutsky <vhutsky>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	dgregor, jgreguske, vhutsky
Target Milestone:	rc	Keywords:	EC2
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 10:24:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Brett Lentz 2011-11-08 21:45:20 UTC

Description of problem:

/usr/sbin/rh-cloud-firstboot.py creates /etc/sysconfig/rh-cloud-firstboot with the context of etc_runtime_t. Restorecon says that it should be etc_t.

Version-Release number of selected component (if applicable): 2.2.19-1.el6


How reproducible: Always


Steps to Reproduce:
1. Install rh-amazon-rhui-client
2. ls -Z /etc/sysconfig/rh-cloud-firstboot
  
Actual results:

-rw-r--r--. root root system_u:object_r:etc_runtime_t:s0 /etc/sysconfig/rh-cloud-firstboot


Expected results:

-rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/sysconfig/rh-cloud-firstboot

Comment 2 Brett Lentz 2011-11-09 15:34:13 UTC

Looks like there's an additional issue with how the rpm handles %config files:

$ restorecon -R -n -v /etc
restorecon reset /etc/yum.repos.d/redhat-us-east.repo.rpmsave context system_u:object_r:initrc_tmp_t:s0->system_u:object_r:etc_t:s0

Comment 3 RHEL Program Management 2011-11-13 06:47:27 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 Jan Kurik 2017-12-06 10:24:34 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/