Bug 1371433
| Summary: | [RFE] Directly instruct NM to avoid controlling and monitoring a device. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Edward Haas <edwardh> | |
| Component: | NetworkManager | Assignee: | Thomas Haller <thaller> | |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.2 | CC: | aloughla, atragler, bgalvani, danken, edwardh, fgiudici, lrintel, mleitner, phoracek, rkhan, sukulkar, thaller, vbenes, ylavi | |
| Target Milestone: | rc | Keywords: | FutureFeature | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | NetworkManager-1.8.0-0.4.rc3.el7 | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1428418 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-01 09:17:07 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: | ||||
| Bug Blocks: | 1393481, 1428418 | |||
|
Description
Edward Haas
2016-08-30 08:22:38 UTC
Is this for devices that are initially setup by NetworkManager but then NM should let them go and not touch them anymore? Can you elaborate on that usecase? Note that device which use (say) DHCP need something to babysit the address leases. How is that supposed to work with NetwokrManager stopping to care about the device? (In reply to Thomas Haller from comment #2) > Is this for devices that are initially setup by NetworkManager but then NM > should let them go and not touch them anymore? Yes > > Can you elaborate on that usecase? Note that device which use (say) DHCP > need something to babysit the address leases. How is that supposed to work > with NetwokrManager stopping to care about the device? Any subsequent implications of taking the device ownership is up to the controller that has requested it. In a simplistic manner, the controller will just define everything from scratch on the device through whichever means it wants (ifcfg, iproute2, netlink). From the NM side, it should try to gracefully cleanup when releasing ownership: In the DHCP case, I guess this involves taking down the dhclient that it spawned or deamonizing that run (if it is not yet so). IMO, killing the dhclient is enough. But it should better not flush existing addresses and other settings. The simplest usecase I can think of is this: - Host networking settings are defined by NM. - Install a controller. - Controller is issued a command to use several devices: - Reads current kernel configuration. - Instructs NM to release ownership of the devices. - Check that NM is not owning it (in case the previous is not blocking) - Controller configures the devices as instructed and owns them. - Controller can return ownership to NM and configure the connection. please review th/device-release-rh1371433 lgtm merged upstream: master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=9e8218f99a2d5a7020703e0fbac1c7c0983930db nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=785b51ed0236b0edcd61c91f9bf3c00d180a9134 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/RHSA-2017:2299 |