Bug 446088

Summary: fuse control filesystem fails to start at boot time
Product: [Fedora] Fedora Reporter: Chris Schembari <cschembari>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8CC: jkubin, lemenkov, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Current Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-14 12:10:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg output with current kernel & 64-bit Sempron CPU. none

Description Chris Schembari 2008-05-12 17:23:06 UTC
Description of problem:  During boot, I get the following error messages:
"Starting fuse" [with no "PASSED" or "FAILED" to the right of it]
"Mounting fuse control filesystem" followed by a red [FAILED]
I have no idea whether this is a serious bug or not, so I'm leaving it at 'low 
severity'.

Version-Release number of selected component (if applicable):
When I dmesg (attached) and grep fuse, I get this:
fuse init (API version 7.9)
SELinux: initialized (dev fusectl, type fusectl), not configured for labeling
SELinux: initialized (dev fusectl, type fusectl), not configured for labeling

How reproducible:  Every time at boot.

Expected results:  Should be no error messages at boot.

Comment 1 Chris Schembari 2008-05-12 17:23:06 UTC
Created attachment 305150 [details]
dmesg output with current kernel & 64-bit Sempron CPU.

Comment 2 Peter Lemenkov 2008-07-12 07:25:45 UTC
Reassigning to selinux-team

Comment 3 Daniel Walsh 2008-07-14 12:10:50 UTC
Since the machine is booting in permissive mode this bug seems to be not related
to selinux.

The only avc's in the log are related to rhgb, which is unrelated.

The fusefs lines should be fixed by updating to the latest selinux-policy.