[Bug 1659195] Re: resolver regression on ubuntu-core from #1636912

[Steve Langasek]

You say that the resolvconf SRU from #1649931 fixed it /mostly/ but not
in all cases.  If you are able to reproduce this problem, can you
provide journalctl output from the affected environment so we can see
what isn't happening in the right order?  Do you have step-by-step
instructions we can follow to reproduce the problem ourselves?

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

Title:
  resolver regression on ubuntu-core from #1636912

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  We had a bunch of test failures in our automatic tests for snapd since this ~Saturday (21.01.2017). All on core, all with errors like:
  """
  error: cannot install "test-snapd-tools": Get https://search.apps.ubuntu.com/api/v1/snaps/details/test-snapd-tools?channel=stable&fields=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_384%2Csummary%2Cdescription%2Cdeltas%2Cbinary_filesize%2Cdownload_url%2Cepoch%2Cicon_url%2Clast_updated%2Cpackage_name%2Cprices%2Cpublisher%2Cratings_average%2Crevision%2Cscreenshot_urls%2Csnap_id%2Csupport_url%2Ctitle%2Ccontent%2Cversion%2Corigin%2Cdeveloper_id%2Cprivate%2Cconfinement: dial tcp: lookup search.apps.ubuntu.com on [::1]:53: read udp [::1]:41766->[::1]:53: read: connection refused
  """

  The key here is the: "dial tcp: lookup search.apps.ubuntu.com on
  [::1]:53: read udp [::1]:41766->[::1]:53: read: connection refused".
  It was random but in the ~150 integration tests we run for the core
  image we had about 5 of those everytime. Further debugging yielded
  that the /etc/resolv.conf is empty when the errors happen.

  It looks like the fix for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912 is
  causing this behaviour for us. Reverting this change gave us stable
  tests again. I also tried to update to the latest resolvconf (the one
  that is reference in #1649931 and also in the followup bug #1649931).
  Using this resolvconf improved the situation dramatically. However we
  still got these errors from time to time with just updating resolvconf
  to the version in xenial-proposed. With the revert of #1649931 we have
  no prolbems so far in our test.

  If there is anything I can try in our image PPA to help with a fix I
  will be happy to do that.

  Thanks,
   Michael

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