Bug 1233482
Summary: | Selinux prevents pod from accessing glusterfs files | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jianwei Hou <jhou> |
Component: | Storage | Assignee: | Mark Turansky <mturansk> |
Status: | CLOSED DUPLICATE | QA Contact: | xjia <xjia> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.0.0 | CC: | bfoster, dmcphers, hchen, libra-bugs, xtian |
Target Milestone: | --- | Keywords: | UpcomingRelease |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-06-19 13:24:18 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
Jianwei Hou
2015-06-19 03:27:05 UTC
Additional: Got same error using hostPath volume when selinux is enforcing I believe this bug is the same as the one linked in my previous comment. Both require SELinux solutions to allow gluster to connect, even though the approach to get there was different between the two. Cut and pasted from an email from Jan Safranek who is working with gluster: To follow up on current development, docker-1.6.2-14.el7 adds a new boolean to SELinux policy. This should allow docker container to access gluster volume (optionally with -P for persistent change): setsebool virt_sandbox_use_fusefs 1 dwalsh told me docker-1.6.2-14.el7 is heading to RHEL 7.1.3, i.e. to be released in couple of days (2015-Jun-23?) in RHEL7 extras channel. So what we need is just to document the boolean and encourage customers to check docker package version (and wait for 1.6.2-14). Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1231936 Docker build: https://brewweb.devel.redhat.com/buildinfo?buildID=441835 Errata: https://errata.devel.redhat.com/advisory/20663 *** This bug has been marked as a duplicate of bug 1231936 *** |