Bug 1520867

Summary: Ensure NetworkManager-wait-online.service is enabled via presets
Product: Red Hat Enterprise Linux 7 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Thomas Haller <thaller>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: atragler, bgalvani, fgiudici, jkoten, jruemker, lmiksik, lrintel, nstraz, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1540243 (view as bug list) Environment:
Last Closed: 2018-02-07 17:11:02 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:
Bug Depends On: 1540243    
Bug Blocks:    

Description Thomas Haller 2017-12-05 10:32:44 UTC 
Previously, we installed a file

  /usr/lib/systemd/system//network-online.target.wants/NetworkManager-wait-online.service

so that network-online.target Wants=NetworkManager-wait-online.service


that has the serious downside that it is impossible to actually disable the service. The only way to prevent if from running was to mask it.


Instead, network-online.target should be enabled on new installatin via presets.

during package upgrade, the spec file contains a %pre section which fixes the enabled status.


Upstream commits are:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d61eaf2545c819cab17c29c4c13a3a3bd94b38a6
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=513d0c2286c8cfe3618cf767da1511bcb939640a

See also Fedora bug 1455704.


All that is left to do, is to ensure that NetworkManager-wait-online.service is enabled via presets.
Comment 2 Thomas Haller 2018-02-07 17:11:02 UTC 
Closing as duplicate, as this is fixed by "redhat-release" package.

*** This bug has been marked as a duplicate of bug 1540243 ***