Merge ~alfonsosanchezbeato/snappy-hwe-snaps/+git/network-manager:fix-route-end-dhcp-lease into ~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager:network-manager/xenial/1.2.2
Proposed by
Alfonso Sanchez-Beato
Status: | Merged |
---|---|
Approved by: | Tony Espy |
Approved revision: | 06511d90695866218578feeff8740298b1034480 |
Merged at revision: | 06511d90695866218578feeff8740298b1034480 |
Proposed branch: | ~alfonsosanchezbeato/snappy-hwe-snaps/+git/network-manager:fix-route-end-dhcp-lease |
Merge into: | ~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager:network-manager/xenial/1.2.2 |
Diff against target: |
123 lines (+21/-20) 1 file modified
src/devices/nm-device.c (+21/-20) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
System Enablement Bot | continuous-integration | Needs Fixing | |
Tony Espy | Approve | ||
Review via email: mp+361207@code.launchpad.net |
Commit message
Make sure default routes survive across expiring of DHCP leases. Commits taken from upstream. Related to LP: #1800712.
Description of the change
Make sure default routes survive across expiring of DHCP leases. Commits taken from upstream. Related to LP: #1800712.
To post a comment you must log in.
The bug you reference says:
FTR, this MP would also help here, although the initially proposed fix for the configuration snap should be enough.
It doesn't sound to me like this is *really* needed? Also the RH bug associated with the first commit isn't viewable w/out a login. ;(-
What version of NM did you cherry pick these fixes from?
Would also mind explaining the actual scenario in some more detail?
It sounds like NM is assuming an existing connection from networkd? And that when this happens, and DHCP leases associated with the connection expire, when a DHCP lease is re-acquired the default route wasn't being restored?
Finally, why is networkd involved here at all? Don't we ship a netplan file which makes NM the default renderer?