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.
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.
This looks good to me.
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)
Both ipv4 and ipv6 addresses are configured and NM is not running. This is working correctly but bug 1260243.
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.