Bug 1331799

Summary:	[1.1] have to restart service to see a device
Product:	Red Hat Enterprise Linux 8	Reporter:	Vladimir Benes <vbenes>
Component:	ModemManager	Assignee:	NetworkManager Development Team <nm-team>
Status:	CLOSED NOTABUG	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.4	CC:	acardace, aloughla, atragler, dcbw, jmaxwell, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-17 15:29:48 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:

Description Vladimir Benes 2016-04-29 14:22:39 UTC

Description of problem:

after installing MM I cannot see already plugged in device. Even doing 
for i in $(ls /sys/bus/usb/devices/usb*/authorized); do echo 0 > $i; done
for i in $(ls /sys/bus/usb/devices/usb*/authorized); do echo 1 > $i; done

doesn't help. I have to restart MM service to make everything working. reboot helps as well :-) The service is active and running after reboot.

Version-Release number of selected component (if applicable):
usb_modeswitch-1.2.7-6.el7.x86_64
ModemManager-1.1.0-8.git20130913.el7.x86_64
NetworkManager-1.2.0-1.el7.x86_64el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.plug in device 
2.install wwan module (and ModemManager and usb_modeswitch)
3. for i in $(ls /sys/bus/usb/devices/usb*/authorized); do echo 0 > $i; done
for i in $(ls /sys/bus/usb/devices/usb*/authorized); do echo 1 > $i; done

Actual results:
nothing, have to restart MM and possibly NM to see device

Expected results:
device should be visible

Additional info:

Comment 1 sushil kulkarni 2017-07-12 11:41:22 UTC

Hi Vlad,

Can you please re-test this to see if this issue happens in 7.4?

Thanks,
Sushil

Comment 2 Vladimir Benes 2018-06-18 11:49:06 UTC

Pavlin,
could you please retest and close if it's not visible with current version?

Thanks you a lot.

Comment 3 Pavlin Georgiev 2018-06-18 14:02:13 UTC

TEST SETUP 1

Distro: RHEL 8.0 Alpha 1
Component version: ModemManager-ModemManager-1.8.0-0.rc2.1.el8+5

TEST PROCEDURE
1. Uninstall ModemManager.
2. Power off the host.
3. Plug broad band modem from Sierra Wireless to a USB port.
4. Power on the host.
5. Install ModemManager and dependent packages.
6. List avable modems with command:
  mmcli -L

Actual result:
error: couldn't find the ModemManager process in the bus

Expected result:
To see the modem attached to the system.

Additional info:
# lsusb -d 1199:68c0
Bus 001 Device 003: ID 1199:68c0 Sierra Wireless, Inc.

# systemctl restart ModemManager
# mmcli -L

No modems were found

When I detach the modem manually and plug it again
then MomdemManager is able to control the device.
# mmcli -L

Found 1 modems:
        /org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless, Incorporated] MBIM [1199:68C0]


OUTCOME
Expected results not achieved.

Comment 4 Pavlin Georgiev 2018-06-18 14:03:44 UTC

TEST SETUP 2

Distro: RHEL 7.6
Component version: ModemManager-1.6.10-1.el7


1. Uninstall ModemManager.
2. Power off the host.
3. Plug broad band modem from Sierra Wireless to a USB port.
4. Power on the host.
5. Install ModemManager and dependent packages.
6. List available modems with command:
  mmcli -L

Actual result:
error: couldn't find the ModemManager process in the bus

Expected result:
To see the modem attached to the system.

Additional info:
# lsusb -d 1199:68c0
Bus 002 Device 003: ID 1199:68c0 Sierra Wireless, Inc. 
# mmcli -L

No modems were found

When I detach the modem manually and plug it again
then ModemManager is able to control the device.
# mmcli -L

Found 1 modems:
        /org/freedesktop/ModemManager1/Modem/0 [Sierra] MBIM [1199:68C0]


OUTCOME
Expected results not achieved.

Comment 5 Marcelo Ricardo Leitner 2019-07-03 15:11:10 UTC

Mass-moving bugs RHEL <= 7.6.0 to 7.7.0.
As we are past RFE deadline for 7.7.0 and we should have no new features on 7.8.0, please evaluate if it's still wanted on RHEL7 and contact PM for exception. You may also move it to RHEL8 if that's wanted. Thanks!

Comment 7 Thomas Haller 2020-03-11 15:26:51 UTC

move bug to rhel-8.

It anyway needs to get fixed there first, before even considering a fix in rhel-7.

Comment 8 Thomas Haller 2020-03-11 15:28:48 UTC

tentatively suggest this bug for RPL-8.3

At least, we should investigate and move this further (even if we may close it as WONTFIX).

Comment 10 Vladimir Benes 2020-07-13 07:35:10 UTC

*** Bug 1331043 has been marked as a duplicate of this bug. ***

Comment 11 Thomas Haller 2020-07-17 15:22:14 UTC

This bug is about that ModemManager needs to be restarted.

Note, that if you install a device plugin in NetworkManager (like NetworkManager-wwan package), then this is also not picked up. Device plugins get only loaded when starting NetworkManager. Reloading them would be interesting, but also relatively complicated. I don't think it has high enough priority to work on this (for NetworkManager).


I cannot speak about ModemManager and whether restart should be handled there. Antonio, what do you think?

Comment 12 Antonio Cardace 2020-07-17 15:29:48 UTC

When installing ModemManager for the first time you also have to reload and apply the new udev rules that get installed with the package, so the correct order is:

$ udevadm control -R
$ udevadm trigger
$ systemctl restart ModemManager
$ systemctl restart NetworkManager

If after these steps then ModemManager doesn't detect the modem there's a bug or the modem is not (yet) supported.

Of course, also a reboot works.

I'm closing this as the behavior seen in the description is normal at the time being.