Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1256772 - NetworkManager quits prematurely with "configure-and-quit"
NetworkManager quits prematurely with "configure-and-quit"
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager (Show other bugs)
7.2
Unspecified Linux
unspecified Severity medium
: rc
: ---
Assigned To: Jirka Klimes
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-25 08:30 EDT by Jirka Klimes
Modified: 2016-01-04 01:04 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-19 06:03:41 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2315 normal SHIPPED_LIVE Moderate: NetworkManager security, bug fix, and enhancement update 2015-11-19 05:06:58 EST

  None (edit)
Description Jirka Klimes 2015-08-25 08:30:50 EDT
NetworkManager quits prematurely when configure-and-quit=yes is in a configuration file. That results in not configuring devices.

Spotted in QE test NetworkManager_Test37_run_once_new_connection.
Comment 1 Jirka Klimes 2015-08-25 08:34:35 EDT
check_if_startup_complete() can be invoked by nm_settings_start() before devices was added and "startup complete" is declared too early.

The fix is available in upstream branch jk/configure-and-quit-fix.
Comment 2 Lubomir Rintel 2015-08-25 11:49:02 EDT
+1

This looks good to me.
Comment 3 Jirka Klimes 2015-08-26 04:02:31 EDT
Committed upstream:
master: 7edb53f core: don't set "startup complete" until devices have been added (rh #1256772)
nm-1-0: 98a5602 core: don't set "startup complete" until devices have been added (rh #1256772)
Comment 5 Vladimir Benes 2015-09-07 04:08:25 EDT
Both ipv4 and ipv6 addresses are configured and NM is not running. This is working correctly but bug 1260243.
Comment 6 errata-xmlrpc 2015-11-19 06:03:41 EST
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/RHSA-2015-2315.html

Note You need to log in before you can comment on or make changes to this bug.