Bug 830781 - AVCs with virsh during automated ricci test on RHEL7
AVCs with virsh during automated ricci test on RHEL7
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Miroslav Grepl
Michal Trunecka
Depends On:
  Show dependency treegraph
Reported: 2012-06-11 08:03 EDT by Michal Trunecka
Modified: 2014-09-30 19:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-06-13 08:41:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Trunecka 2012-06-11 08:03:30 EDT
Description of problem:
When running automated test selinux-policy/Regression/bz761592-ricci-and-similar following AVC showed up. All other parts of the test PASSed.

time->Mon Jun 11 07:55:35 2012
type=SYSCALL msg=audit(1339415735.048:731): arch=c000003e syscall=2 success=no exit=-13 a0=7f65258656ca a1=80000 a2=1b6 a3=238 items=0 ppid=24887 pid=25139 auid=4294967295 uid=994 gid=0 euid=994 suid=994 fsuid=994 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="virsh" exe="/usr/bin/virsh" subj=system_u:system_r:virsh_t:s0 key=(null)
type=AVC msg=audit(1339415735.048:731): avc:  denied  { read } for  pid=25139 comm="virsh" name="passwd" dev="dm-1" ino=49630 scontext=system_u:system_r:virsh_t:s0 tcontext=system_u:object_r:passwd_file_t:s0 tclass=file

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

How reproducible:
by automated test

Actual results:

Expected results:
Comment 1 Daniel Walsh 2012-06-11 10:15:29 EDT
Fixed in selinux-policy-3.10.0-130.fc17
Comment 3 Ludek Smid 2014-06-13 08:41:09 EDT
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.

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