Bug 1316917 - Using docker interfaces in rhel distro policy breaks selinux-policy rpm build
Summary: Using docker interfaces in rhel distro policy breaks selinux-policy rpm build
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On: 1304322
Blocks: 1236580
TreeView+ depends on / blocked
 
Reported: 2016-03-11 13:35 UTC by Lukas Vrabec
Modified: 2016-11-04 02:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 02:44:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2283 0 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2016-11-03 13:36:25 UTC

Description Lukas Vrabec 2016-03-11 13:35:35 UTC 
Description of problem:
During selinux-policy build, there is no docker.if file available in build root so 

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-65.el7

How reproducible:
always


Actual results:
docker interface file is not available during selinux-policy build

Expected results:
docker interface file is available during selinux-policy build

Additional info:
We need to attach docker interface file to distgit before every new build like we do it in Fedora 24 distgit.
Comment 1 Lukas Vrabec 2016-03-11 14:20:30 UTC 
After discussion with Mirek, we need new userspace for this bug and make some changes also in docker.spec file.
Comment 9 errata-xmlrpc 2016-11-04 02:44:48 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://rhn.redhat.com/errata/RHBA-2016-2283.html
Note You need to log in before you can comment on or make changes to this bug.