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.

Description of problem:
When NetworkManager service is stopped, nmcli hangs in multiple situations after raising an exception to stdout.

Such a hang is very unpleasant for tools or scripts running nmcli command and expecting (prompt) output.


Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-66.el6.x86_64


How reproducible:
100%


Steps to Reproduce:
1. service NetworkManager stop
2. nmcli con status
3. nmcli con show
4. nmcli con --help
5. nmcli con whateverWrong


Actual results:
commands 2. to 5. hung after raising:

** (process:18982): WARNING **: get_all_cb: couldn't retrieve system settings properties: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.

** (process:18982): WARNING **: fetch_connections_done: error fetching system connections: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.


Expected results:
Commands should not hung.


Additional info:

nmcli only hangs when neither NetworkManager nor nm-applet is running. NetworkManager 0.8 (in RHEL 6) has two setting services supplying connections: one is NetworkManager itself handling system connections, and the other is a user service handling user connections - usually nm-applet. From NetworkManager 0.9 upwards all connections are managed by NetworkManager itself.

Also note that nmcli commands in RHEL6 differ from RHEL7. For example:
List all connections:
nmcli con [show]                - RHEL7
nmcli con list [user | system]  - RHEL6

Active connections:
nmcli con show -a               - RHEL7
nmcli con status                - RHEL6 

But, of course, the nmcli freeze is a bug and I will post a patch to fix it.

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://rhn.redhat.com/errata/RHBA-2015-1257.html