Bug 711771

Summary: Wrong permissions produce error in lock file for modem while opening Mobile modem
Product: [Fedora] Fedora Reporter: Andres Villarreal <avillarrealpouw>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw, mike.dyer
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: 2012-08-07 16:01:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Andres Villarreal 2011-06-08 12:52:59 UTC
Description of problem:
When a ZTE 628 mobile modem is inserted to the USB port the activation procedure for the modem ends with the error (in /var/log/messages):

Jun  7 22:49:48 av pppd[21767]: Can't create lock file /var/lock/LCK..ttyUSB2: Permission denied

and NetworkManager fails to connect the modem to the network.

Version-Release number of selected component (if applicable):
Fedora release 15 (Lovelock)

How reproducible:
Always fails.

Steps to Reproduce:
1. After opening a session in gnome (version 3) insert the mobile modem
2. Check /var/log/messages
3. Expanding the NetworkManager icon you see that it tries to connect several times and never connects.
  
Jun  7 22:53:06 av NetworkManager[791]: <warn> GSM connection failed: (32) Serial command timed out
Jun  7 22:53:06 av NetworkManager[791]: <info> (ttyUSB2): device state change: prepare -> failed (reason 'unknown') [40 120 1]
Jun  7 22:53:06 av NetworkManager[791]: <warn> Activation (ttyUSB2) failed.
Jun  7 22:53:06 av NetworkManager[791]: <info> (ttyUSB2): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun  7 22:53:06 avillarrlap3 NetworkManager[791]: <info> (ttyUSB2): deactivating device (reason: 0).


Actual results:
Modem will not connect. The error above will appear in messages.
Also, the following errors occur with selinux:

messages-20110605:Jun  4 15:44:55 av kernel: [    7.111706] type=1400 audit(1307202280.141:4): avc:  denied  { relabelto } for  pid=1 comm="systemd" name="lock" dev=tmpfs ino=6212 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:pppd_t:s0 tclass=dir
messages-20110605:Jun  4 15:44:55 av kernel: [   19.109172] type=1400 audit(1307220292.140:5): avc:  denied  { read } for  pid=744 comm="systemd-tmpfile" name="lock" dev=dm-1 ino=1985 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=lnk_file
messages-20110605:Jun  4 15:44:55 av kernel: [   19.121304] type=1400 audit(1307220292.152:6): avc:  denied  { relabelto } for  pid=744 comm="systemd-tmpfile" name="lock" dev=tmpfs ino=6212 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:pppd_t:s0 tclass=dir
messages-20110605:Jun  4 15:44:55 av kernel: [   19.121453] type=1400 audit(1307220292.152:7): avc:  denied  { associate } for  pid=744 comm="systemd-tmpfile" name="lock" dev=tmpfs ino=6212 scontext=system_u:object_r:pppd_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=filesystem


Expected results And Workaround:
I have been able to eliminate the error by doing the following:
- change selinux from "enforcing" to "permissive"
- stop NetowrkManager (service NetworkManager stop)
- stop modem-manager (killall -9 modem-manager)
- start modem-manager in one terminal as root (modem-manager --debug --log-level=DEBUG)
- start NetworkManager as root in another terminal (NM_PPP_DEBUG=1 /usr/sbin/NetworkManager --no-daemon)

The lock file that is created is "/var/lock/LCK..ttyUSB2" (user root, group root, write permissions only for root) but should be the correct one for the
release (something like /var/lock/lockdev/ttyUSB2 ???).

Comment 1 Fedora End Of Life 2012-08-07 16:01:15 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping