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/1649931 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.
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: /search. apps.ubuntu. com/api/ v1/snaps/ details/ test-snapd- tools?channel= stable& fields= anon_download_ url%2Carchitect ure%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
"""
error: cannot install "test-snapd-tools": Get https:/
"""
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/1649931 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