Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1698495

Summary: nmcli crashing when upping gsm connection
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.7CC: atragler, bgalvani, fgiudici, lrintel, pgeorgie, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.18.0-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:16:56 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:
Attachments:
Description Flags
[PATCH] clients: fix assertion when requesting gsm pin secret
none
Log from NetworkManager none

Description Vladimir Benes 2019-04-10 13:26:08 UTC 
Description of problem:
nmcli  connection add type gsm ifname \* con-name gsm apn internet

[root@gsm-r5s4-01 ~]# nmcli  connection up id gsm 
**
libnmc:ERROR:clients/common/nm-secret-agent-simple.c:171:_secret_real_new_plain: assertion failed: ((secret_type == NM_SECRET_AGENT_SECRET_TYPE_SECRET) == nm_setting_get_secret_flags (setting, property, ((void *)0), ((void *)0)))
Aborted (core dumped)


Version-Release number of selected component (if applicable):
kernel-3.10.0-1037.el7.rh1630402.x86_64
NetworkManager-1.18.0-0.3.20190408git43d9187c14.el7.x86_64
ModemManager-1.6.10-1.1.bz1630402.el7.x86_64
Comment 3 Beniamino Galvani 2019-04-10 15:39:36 UTC 
Created attachment 1554276 [details]
[PATCH] clients: fix assertion when requesting gsm pin secret
Comment 5 Thomas Haller 2019-04-10 15:53:26 UTC 
(In reply to Beniamino Galvani from comment #3)
> Created attachment 1554276 [details]
> [PATCH] clients: fix assertion when requesting gsm pin secret

lgtm.


Note that the commit message says "Fixes: 0601b5d725b0", but the bug was already there from the beginning: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=3bda3fb60c104114192e4e3c9c4ba0bef84d3a00 -- namely, that this had "secret=FALSE", while it is a secret. Only now with the assertion it breaks.
Comment 6 Beniamino Galvani 2019-04-11 11:57:53 UTC 
Amended commit message and applied:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/a94ccc9acc47f08943f017a5040abeb05afee183
Comment 8 Pavlin Georgiev 2019-05-07 15:06:57 UTC 
Created attachment 1565265 [details]
Log from NetworkManager
Comment 9 Pavlin Georgiev 2019-05-07 15:11:40 UTC 
TEST SETUP
Distro: RHEL-7.7-20190502.1
Testing machine: gsm-r6s16-01.wlan.rhts.eng.bos.redhat.com
Broadband modem: Zoom 4995


Component version:
kernel-3.10.0-1040.el7.x86_64                                                       
NetworkManager-1.18.0-1.el7.x86_64                                                  
ModemManager-1.6.10-1.el7.x86_64 


TEST PROCEDURE
# nmcli dev
DEVICE   TYPE      STATE         CONNECTION
eth0     ethernet  connected     System eth0
ttyUSB2  gsm       disconnected  --

# nmcli connection add type gsm ifname \* con-name gsm apn internet
Connection 'gsm' (695ed2b9-084a-4a58-aab6-c35f8b30925a) successfully added.

# nmcli  connection up id gsm
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)


RESULT
Upgrading component: component_name
    from: 1.18.0-0.3.20190408git43d9187c14.el7
      to: 1.18.0-1.el7
has fixed the bug.
Comment 10 Pavlin Georgiev 2019-05-08 05:14:09 UTC 
TEST PROCEDURE 2
1. The gsm connection already exists in NetworkManager.
2. Assign a PIN code to the SIM card.
3. Reboot the testing machine (or disconnect the modem manually).
4. Activate the connection by entering the PIN:
  # nmcli  --ask connection up id gsm
  PIN code is needed for the mobile broadband device
  PIN (gsm.pin): ••••
5. Show active connections:
  # nmcli con show
  NAME         UUID                                  TYPE      DEVICE  
  System eth0  c6d197fc-3e10-49fe-b78d-d70fabb722f9  ethernet  eth0    
  gsm          53d11896-2092-48a8-b667-a86587600d0e  gsm       ttyUSB2


RESULT
There are no errors.
Comment 12 errata-xmlrpc 2019-08-06 13:16:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2302