Bug 1369159

Summary: label /var/lib/kubelet svirt_sandbox_file_t
Product: Red Hat Enterprise Linux 7 Reporter: Eric Paris <eparis>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: high    
Version: 7.3CC: agoldste, dapospis, dwalsh, eparis, jrogers, kajtzu, lvrabec, mgrepl, mmalik, plautrba, pmorie, pvrabec, ssekidde
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-95.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1369168 (view as bug list) Environment:
Last Closed: 2016-11-04 02:37:33 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:
Bug Depends On:    
Bug Blocks: 1369168    

Description Eric Paris 2016-08-22 14:38:12 UTC
We need to have /var/lib/kubelet labeled as svirt_sandbox_file_t because we do container data storage under that location.

Comment 4 Lukas Vrabec 2016-09-07 08:32:47 UTC
Guys, 
Please make deal which label is better and right for /var/lib/kubelet. 

Dan, 
If this solution is wrong, please switch it to ASSIGNED. 

Thanks.

Comment 5 Eric Paris 2016-09-08 02:50:44 UTC
one label works, one label just flat is impossible to use. We go with my way to solve the (many) real customer issues now. pmorie/dwalsh can work this week to look for a better long term solution which is likely to require extensive userspace rewrites. Which take a long time to get upstream. But for now, I know Dan doesn't like it, but sandbox_file_t:s0 on /var/lib/kubelet.

Comment 6 Daniel Walsh 2016-09-08 19:27:33 UTC
Paul Morie and I had a talk on bluejeans, and I believe just changing kubernetes to always specify the :Z will fix the issue.

Comment 8 errata-xmlrpc 2016-11-04 02:37:33 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