friendly-recovery

Merge lp://qastaging/~jawn-smith/friendly-recovery/systemd-resolvconf-conflict into lp://qastaging/~ubuntu-core-dev/friendly-recovery/ubuntu

  1. systemd-resolvconf-conflict
  2. Merge into ubuntu
Proposed by William Wilson
Status: Merged
Merged at revision: 167
Proposed branch: lp://qastaging/~jawn-smith/friendly-recovery/systemd-resolvconf-conflict
Merge into: lp://qastaging/~ubuntu-core-dev/friendly-recovery/ubuntu
Diff against target: 35 lines (+7/-2)
2 files modified
debian/changelog (+6/-1)
lib/recovery-mode/options/network (+1/-1)
To merge this branch: bzr merge lp://qastaging/~jawn-smith/friendly-recovery/systemd-resolvconf-conflict
Reviewer Review Type Date Requested Status
Brian Murray Needs Information
Dimitri John Ledkov (community) lgtm Approve
Review via email: mp+396944@code.qastaging.launchpad.net

Description of the change

Adding resolvconf-pull-resolved.path to the network script. This resolves a conflict between systemd-resolved and resolvconf that was resulting in failed DNS resolution in friendly recovery mode.

To post a comment you must log in.
Revision history for this message
Dimitri John Ledkov (xnox) :
review: Approve (lgtm)
lp://qastaging/~jawn-smith/friendly-recovery/systemd-resolvconf-conflict updated
168. By William Wilson

Reverting the maintainer as this will go to debian

Revision history for this message
Brian Murray (brian-murray) wrote :

What will happen in the event that "resolvconf-pull-resolved.path" does not exist on disk? Will systemctl start exit abnormally?

review: Needs Information

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches