Merge ~morphis/snappy-hwe-snaps/+git/network-manager:move-dhcp-leases into ~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager:master
Status: | Merged |
---|---|
Approved by: | Simon Fels |
Approved revision: | fc93640aea921f0ffae2f03ccb00bda7c9d313ab |
Merged at revision: | 6a9f9e50b11cfd1e735388b6f85e50cd4ed6ce45 |
Proposed branch: | ~morphis/snappy-hwe-snaps/+git/network-manager:move-dhcp-leases |
Merge into: | ~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager:master |
Prerequisite: | ~morphis/snappy-hwe-snaps/+git/network-manager:remove-netplan-completely |
Diff against target: |
134 lines (+83/-2) 4 files modified
bin/dhcp-lease-mover (+26/-0) bin/networkmanager (+9/-2) snapcraft.yaml (+16/-0) tests/main/dhcp-leases-are-moved/task.yaml (+32/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
System Enablement Bot | continuous-integration | Approve | |
Jim Hodapp (community) | Approve | ||
Alfonso Sanchez-Beato | Approve | ||
Review via email: mp+309847@code.launchpad.net |
This proposal supersedes a proposal from 2016-11-02.
Description of the change
Add transitioning of DHCP lease files from SNAP_DATA to /run
The current implementation stores DHCP lease files inside /run which means they are lost after rebooting the system. This can lead to problems with losing a previously assigned IP address if the lease is still valid. We can't just simply move the leases back to SNAP_DATA as probert/
This is based on top of https:/
PASSED: Continuous integration, rev:e35d68a18ec 2610fbb3551ee6f 770110c39086a2 /jenkins. canonical. com/system- enablement/ job/generic- build-snap/ 245/ /jenkins. canonical. com/system- enablement/ job/generic- update- snap-mp/ 147/console
https:/
Executed test runs:
None: https:/
Click here to trigger a rebuild: /jenkins. canonical. com/system- enablement/ job/generic- build-snap/ 245/rebuild
https:/