Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 973776 - AVC denial when attaching volume to RHOS 3 instance
AVC denial when attaching volume to RHOS 3 instance
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy (Show other bugs)
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: Miroslav Grepl
Milos Malik
: ZStream
Depends On: 971594
Blocks: 965311
  Show dependency treegraph
Reported: 2013-06-12 13:31 EDT by Chris Pelland
Modified: 2016-04-26 11:31 EDT (History)
10 users (show)

See Also:
Fixed In Version: selinux-policy-3.7.19-195.el6_4.11
Doc Type: Bug Fix
Doc Text:
Previously, SELinux returned AVC denial messages during attempts to attach an LVM volume to a Red Hat OpenStack 3 instance. The relevant SELinux policy rules have been modified to add an additional MCS attribute for hald_t SELinux domain, and AVC denial messages are no longer returned when attaching LVM volume to a Red Hat OpenStack 3 instance.
Story Points: ---
Clone Of:
Last Closed: 2013-06-27 14:06:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1000 normal SHIPPED_LIVE selinux-policy bug fix update 2013-06-27 18:05:25 EDT

  None (edit)
Description Chris Pelland 2013-06-12 13:31:34 EDT
This bug has been copied from bug #971594 and has been proposed
to be backported to 6.4 z-stream (EUS).
Comment 4 Miroslav Grepl 2013-06-13 02:04:58 EDT
Fixed in selinux-policy-3.7.19-195.el6_4.11
Comment 8 Miroslav Grepl 2013-06-19 08:15:55 EDT
How does the testing look?
Comment 12 errata-xmlrpc 2013-06-27 14:06:21 EDT
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.


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