[Bug 1716833] Re: NM manages /etc/resolv.conf directly in artful after removal of resolvconf

Dimitri John Ledkov launchpad at surgut.co.uk
Sun Sep 17 15:21:34 UTC 2017


So if /etc/resolv.conf was pointing at stub-resolv.conf everything would
have worked.

However, at closer inspection, netplan test suite has also been miss
detecting the backends used by NetworkManager and whether or not
resolved was enabled. For resolved, it was only considering nss module
and was not checking if stub resolver is enabled. After updating the
checks for backend detection the tests started to pass both on fixed and
broken hosts.

** Package changed: network-manager (Ubuntu Artful) => nplan (Ubuntu
Artful)

** Changed in: nplan (Ubuntu Artful)
       Status: Triaged => Fix Released

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

Title:
  NM manages /etc/resolv.conf directly in artful after removal of
  resolvconf

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Artful:
  Fix Released

Bug description:
  The nplan autopkgtests are now failing in artful following the removal
  of resolvconf from the base system, with the following error:

  ======================================================================
  FAIL: test_manual_addresses (__main__.TestNetworkManager)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/tmp/autopkgtest.4I4oae/build.Xcu/nplan-0.26/tests/integration.py", line 1110, in test_manual_addresses
      self.assertRegex(resolv_conf, 'search.*fakesuffix')
  AssertionError: Regex didn't match: 'search.*fakesuffix' not found in '# Generated by NetworkManager\nnameserver 127.0.1.1\n'

  
  It is possible that there is *also* a bug with nplan's integration with systemd-resolved; however, what this error message exposes is that NM is overwriting /etc/resolv.conf when this should now be managed by systemd-resolved instead.

  NM needs to inject its DNS server information into resolved instead of
  editing /etc/resolv.conf directly.

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



More information about the foundations-bugs mailing list