[Bug 1689410] Re: nplan with networkd + resolvconf without resolved, results in no DNS resolution

[Steve Langasek]

Hi Ryan,

On Tue, May 09, 2017 at 02:20:17PM -0000, Dimitri John Ledkov wrote:

> <rharper> it does create the yaml and call generate, but it's not
> sufficient to create the symlink IIRC due to the code in netplan which
> doesn't generate the symlinks in /run if it;s not invoked as a genartor

There is no bug report at https://bugs.launchpad.net/ubuntu/+source/nplan
for this.  Is there one on cloud-init?

> <rharper> I've picked this apart too many times;  we've got the set of
> changes needed documented and staged for ubuntu-core

Where are these staged?

> <rharper> but it's not landed in xenial for cloud-init proper due to not
> wanting to foist networkd onto xenial users at this time

I don't understand this.  Why would any of these staged changes not be
conditional on use of nplan, thus avoiding any "foisting"?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1689410

Title:
  nplan with networkd + resolvconf without resolved, results in no DNS
  resolution

Status in ifupdown package in Ubuntu:
  Invalid
Status in nplan package in Ubuntu:
  Invalid
Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  if nplan yaml specifies nameservers which are passed onto networkd,
  they will never take effect on systems that do not use systemd-
  resolved.

  This is because there is no integration between nplan and resolvconf,
  either directly; via networkd; via NetworkManager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1689410/+subscriptions