Bug 1459844

Summary: qemu_blk_image and qemu_file_image plugins should also match AVCs where source type = svirt_t
Product: Red Hat Enterprise Linux 7 Reporter: Milos Malik <mmalik>
Component: setroubleshootAssignee: Vit Mojzis <vmojzis>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: lmiksik, lvrabec, mgrepl, mmalik, plautrba
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1459835
: 1649838 (view as bug list) Environment:
Last Closed: 2018-10-30 09:47:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milos Malik 2017-06-08 10:43:08 UTC
Description of problem:
* both qemu_blk_image and qemu_file_image plugins match only AVCs where source type is qemu_t, but qemu_t is an alias for svirt_t on RHEL-7
* as a result the report from qemu_blk_image or qemu_file_image plugins never appears in the output of sealert

# seinfo -tqemu_t -x
   TypeName svirt_t
   Aliases
      qemu_t
#

Version-Release number of selected component (if applicable):
setroubleshoot-server-3.2.28-3.el7.x86_64
setroubleshoot-plugins-3.0.65-1.el7.noarch

How reproducible:
* always

Steps to Reproduce:
1. get a RHEL-7.3 or RHEL-7.4 machine (targeted policy is active)
2. run following automated TC:
 * /CoreOS/setroubleshoot-plugins/Sanity/qemu_blk_image
 * /CoreOS/setroubleshoot-plugins/Sanity/qemu_file_image
3. sealert -l '*'

Actual results:
 * the report from qemu_blk_image or qemu_file_image plugin does NOT appear in the output of sealert

Expected results:
 * the report from qemu_blk_image or qemu_file_image plugin appears in the output of sealert

Comment 6 errata-xmlrpc 2018-10-30 09:47:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3100