Bug 537745
| Summary: | SELinux is preventing /usr/sbin/NetworkManager "write" access on /var/lib. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | ojab <bugzilla.redhat.com> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | aktigger99645, andrewwatty, antanassss, balabalkhande, bmaringanti, carlositlamar, chrisa1, dakshay, dcbw, devadatta.dev, diegowalisson, dkrawchuk, dwalsh, eceprince, eddymurphy, eduard0.ec0, FAJ83, gbrathwaite7thd, georgewu2007, ghisha, giomammino, harley.goode, inboxacct2, jake, james, jaroslaw.gorny, jhnhgs75, johannbg, josephcaseley, kruvalig, linuxnow, mail, marcelob55, markhuomian, mgrepl, misek, muhammad.baiquni, olivares14031, omarberroteranlkf, one.call.merch, p-fenton1, redhat, richard.hogaboom, riverstank420, sarrab1976, satishs2, skotchman, sthomas113, tadej.j, tombonius, toxn, wrightman84 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | setroubleshoot_trace_hash:15c4eceb6747753dc6876f84aa0bc3644605eba3fde943af1a11b7b35d2b4c4a | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-02-05 21:01:43 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: | |||
|
Description
ojab
2009-11-16 06:43:01 UTC
Is NetworkManager trying to create the wicd dir? Or is this something new? If it is the wicd dir, you can create the dir and restorecon it and networkmanager should work fine. This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I don't really know, all work just fine, but SELinux zenity popup has appeared. Dan any ideas? Yeah, we now write some state files to /var/lib/NetworkManager. That's now in F13/devel and F12-updates-testing. Dan, Keep me informed when you create new directories that network manager needs to write to. Fixed in selinux-policy-3.6.32-47.fc12.noarch BTW /var/lib/NetworkManager should be in the payload. Sorry, will do. Good point, I will add that dir to the RPM for the next round of updates. Note that this has not hit F12 yet, so by the time it does, the SELinux rules will be out. Thanks! This bug has now been seen on F11 system, brought on by NetworkManager.i586 1:0.7.2-1.fc11 update. Yeah, patch was backported to F11 as well; I need to do better keeping dwalsh informed... Miroslav, can you get an update out for this fast. Added to selinux-policy-3.6.12-92.fc11 works now with latest versions *** Bug 545726 has been marked as a duplicate of this bug. *** Updated Fedora 11 Leonidas exhibited issue on 14 December. 2.6.30.9-102.fc11.i686.PAE Update results in: selinux-policy-3.6.12-91.fc11 I had just logged in and noticed the SELinux icon. This has been accumulating violations before I logged in. I am experiencing this same bug in F11. I am running selinux-policy-3.6.12-92.fc11 and kernel 2.6.30.9-102.fc11.i586. I tried restorecon -v '/var/lib' but the context remained system_u:object_r:var_lib_t:s0. /var/lib/NetworkManager however has the context system_u:object_r:NetworkManager_var_lib_t:s0 which I assume is right. Interestingly NetworkManager connects faster and more reliably with this bug in effect. Hi there, Just to report that today's update >> selinux-policy-3.6.12-92.fc11 << fixed the problem on my system. Thanks. BTW. kernel 2.6.30.9-102.fc11.i586 (In reply to comment #17) > I am experiencing this same bug in F11. I am running > selinux-policy-3.6.12-92.fc11 and kernel 2.6.30.9-102.fc11.i586. I tried > restorecon -v '/var/lib' but the context remained > system_u:object_r:var_lib_t:s0. /var/lib/NetworkManager however has the > context system_u:object_r:NetworkManager_var_lib_t:s0 which I assume is right. > Interestingly NetworkManager connects faster and more reliably with this bug in > effect. It is fixed now. I'm afraid that it has returned. I started getting boot errors referencing NetworkManager,"** (NetworkManager:1669): WARNING **: State file /var/lib/NetworkManager/NetworkManager.state parsing failed: (2) Failed to create file '/var/lib/NetworkManager/NetworkManager.state.M14J6U': Permission denied." as well as the SELinux alert mentioned in comment 1. This started after I changed it from DHCP to a static IP manually. The network is working inspite of the errors/warnings. What does restorecon -R -v /var/lib/NetworkManager Output? restorecon reset /var/lib/NetworkManager context system_u:object_r:var_lib_t:s0->system_u:object_r:NetworkManager_var_lib_t:s0 Looks like that may have fixed it, I'll try a reboot to see if it works. Okay, no more boot errors and no new SELinux alert. The old SELinux Troubleshooter used to display suggested "fixes", this new one doesn't seem to. I'm never sure what options to use. Yes, if something is removing this file and recreating it, we have a bug. I meant directory. Yes, if something is removing this directory (/var/lib/NetworkManager) and recreating it, we have a bug. hi update's have fix it for me thanks Thanks, closing. |