Bug 236189 - SELinux denied access request by /usr/sbin/hcid
Summary: SELinux denied access request by /usr/sbin/hcid
Status: CLOSED DUPLICATE of bug 236089
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy   
(Show other bugs)
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-12 12:40 UTC by Uwe Kubosch
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-21 11:15:56 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
The SELinux alert (2.32 KB, text/plain)
2007-04-12 12:40 UTC, Uwe Kubosch
no flags Details

Description Uwe Kubosch 2007-04-12 12:40:39 UTC
Description of problem:
SELinux denied access request by /usr/sbin/hcid

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

How reproducible:
Happens when i do a 'yum upgrade' right after installation from DVD (prime).

Steps to Reproduce:
1. Install FC7 6.92 prime with office+development+web server
2. Choose default settings on SELinux in first-boot
3. run 'yum upgrade'
Actual results:
I get an alert from SELinux that hcid is not allowed access  "read" to inotify

Expected results:
No alert.

Additional info:
I included the SELinux alert

Comment 1 Uwe Kubosch 2007-04-12 12:40:39 UTC
Created attachment 152439 [details]
The SELinux alert

Comment 2 Matthew Miller 2007-04-12 12:58:24 UTC
Although it's far from obvious, all Fedora 7 test bugs should be filed against
"devel", not "test#". Moving this, so it doesn't get lost.

This has been a bulk message. We return you now to your regularly scheduled
program, already in progress.

Comment 3 David Woodhouse 2007-07-21 11:15:56 UTC

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

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