Bug 710437

Summary: Satellite sync cache has inconsistent selinux type
Product: Red Hat Satellite 5 Reporter: Šimon Lukašík <slukasik>
Component: Satellite SynchronizationAssignee: Michael Mráka <mmraka>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 541CC: cperry, jhutar, mminar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-04 13:26:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 462714    

Description Šimon Lukašík 2011-06-03 11:52:40 UTC
Description of problem:
The content in /var/cache/rhn/satsync/ is created with 

    unconfined_u:object_r:spacewalk_cache_t

by satellite-sync. On the other hand selinux politics specifies

    system_u:object_r:var_t

for that directory. The selinux type for this content should be
consistent.


Version-Release number of selected component (if applicable):
RHN Satellite 5.4.0
RHN Satellite 5.4.1

How reproducible:
always

Steps to Reproduce:
1. satellite-sync some channel
2. restorecon -rvv /var/cache/rhn/
3.
  
Actual results:
Thousands of lines similar to:
  restorecon reset /var/cache/rhn/satsync/packages/38/rhn-package-620138
  context unconfined_u:object_r:spacewalk_cache_t:s0->
  system_u:object_r:var_t:s0


Expected results:
<dark silence>

Additional info:
This is revealed by each update of spacewalk-selinux.

Comment 1 Miroslav Suchý 2011-06-20 15:41:29 UTC
I could not confirm it.
Do you have some special setup? Like nfs mounted var?

Comment 2 Šimon Lukašík 2011-06-21 07:53:10 UTC
Mirek, you are right. My reproducer is incorrect. You need to have fresh
installation *or* remove

    rm -rf /var/cache/rhn/satsync/

prior the sync. The problem might appear to user, when he: (1) installs
Satellite 5.4.0, (2) Sync some arbitrary channel, (3) Runs yum update of
spacewalk-selinux.