Bug 912140

Summary:	No longer mounts automatically at boot
Product:	[Fedora] Fedora	Reporter:	Michael Cronenworth <mike>
Component:	selinux-policy	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	dominick.grift, dwalsh, joe, jonathansteffan, kkeithle, mgrepl, silas
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-14 03:02:16 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 Michael Cronenworth 2013-02-17 20:38:18 UTC

Description of problem:
With GlusterFS 3.2 and Fedora 17, my client would automatically mount multiple gluster volumes at boot. After upgrading the server and client to Fedora 18 (GlusterFS 3.3) the client no longer mounts them and I have to mount them manually.


Version-Release number of selected component (if applicable): 
glusterfs-3.3.1-9.fc18.x86_64
glusterfs-fuse-3.3.1-9.fc18.x86_64


How reproducible: Always


Steps to Reproduce:
1. Add entries to fstab:
10.0.0.1:/michael            /media/michael	glusterfs   defaults,_netdev    0 0
10.0.0.1:/media              /media/media	glusterfs   defaults,_netdev    0 0
2. Reboot
  
Actual results: No volumes are mounted.


Expected results: Volumes should be mounted.


Additional info: The client is setup with a static IP address.

Comment 1 Michael Cronenworth 2013-03-05 00:47:14 UTC

I now know this is a SELinux denial. When I set the client to Permissive mode the gluster mount is mounted at boot. I get the following audit message during boot.

type=1400 audit(1362443230.416:5): avc:  denied  { execute_no_trans } for  pid=1262 comm="mount.glusterfs" path="/usr/sbin/glusterfsd" dev="md0" ino=3283438 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:glusterd_exec_t:s0 tclass=file

selinux-policy-3.11.1-82.fc18.noarch

Comment 2 Miroslav Grepl 2013-03-05 10:06:05 UTC

Fixed in selinux-policy-3.11.1-84.fc18.noarch

Comment 3 Fedora Update System 2013-03-08 16:11:26 UTC

selinux-policy-3.11.1-84.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-84.fc18

Comment 4 Fedora Update System 2013-03-08 23:59:17 UTC

Package selinux-policy-3.11.1-84.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-84.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3605/selinux-policy-3.11.1-84.fc18
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-03-12 23:38:32 UTC

Package selinux-policy-3.11.1-85.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-85.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3605/selinux-policy-3.11.1-85.fc18
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-03-14 03:02:19 UTC

selinux-policy-3.11.1-85.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.