Bug 222300 - CDROM test fails. SELinux security violation
CDROM test fails. SELinux security violation
Status: CLOSED DUPLICATE of bug 218124
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Test Suite (tests) (Show other bugs)
5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Greg Nichols
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-11 10:43 EST by Gregory Feiner
Modified: 2008-07-16 17:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-01-11 15:54:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
CDROM test results. (742.76 KB, application/octet-stream)
2007-01-11 10:43 EST, Gregory Feiner
no flags Details
SELinux sercurity violation during CDROM test. (1.83 KB, text/plain)
2007-01-11 10:44 EST, Gregory Feiner
no flags Details

  None (edit)
Description Gregory Feiner 2007-01-11 10:43:45 EST
Description of problem:
CDROM test fails. The error is: cp: cannot create directory `./device-
copy':Permission denied.  At the same time, SELinux pops up with a security 
violation stating: SELinux is preventing /bin/cp (iso9660_t) "associate" to 
device-copy (fs_t).

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


How reproducible: Every time.


Steps to Reproduce:
1. Install RHEL 5 to ProLiant DL320 G5.
2. Install HTS 5.0-15.  
3. Run CDROM test.  watch it fail.  The CDROM is model 224E_N
  
Actual results:


Expected results: should pass.


Additional info: results rpm and SELinux log are attached.
Comment 1 Gregory Feiner 2007-01-11 10:43:45 EST
Created attachment 145360 [details]
CDROM test results.
Comment 2 Gregory Feiner 2007-01-11 10:44:22 EST
Created attachment 145361 [details]
SELinux sercurity violation during CDROM test.
Comment 3 Gregory Feiner 2007-01-11 14:53:37 EST
Garry Wong has found that changing the SELinux Enforcement to Permissive gets 
past this problem.  However, according to documentation, Enforced is 
required.  Given this, is this workaround valid?
Comment 4 Greg Nichols 2007-01-11 15:54:44 EST

*** This bug has been marked as a duplicate of 218124 ***

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