2017-08-12 19:45:53 |
WoJ |
bug |
|
|
added bug |
2017-08-14 10:19:53 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Zesty |
|
2017-08-14 10:19:53 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Zesty) |
|
2017-08-14 10:19:53 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Artful |
|
2017-08-14 10:19:53 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Artful) |
|
2017-08-14 10:19:58 |
Dimitri John Ledkov |
systemd (Ubuntu Artful): status |
New |
Fix Committed |
|
2017-08-14 10:20:01 |
Dimitri John Ledkov |
systemd (Ubuntu Zesty): status |
New |
Triaged |
|
2017-08-14 10:20:03 |
Dimitri John Ledkov |
systemd (Ubuntu Zesty): importance |
Undecided |
High |
|
2017-08-14 10:20:05 |
Dimitri John Ledkov |
systemd (Ubuntu Artful): importance |
Undecided |
High |
|
2017-08-14 10:20:08 |
Dimitri John Ledkov |
systemd (Ubuntu Artful): assignee |
|
Dimitri John Ledkov (xnox) |
|
2017-08-14 10:20:09 |
Dimitri John Ledkov |
systemd (Ubuntu Zesty): assignee |
|
Dimitri John Ledkov (xnox) |
|
2017-08-14 10:20:12 |
Dimitri John Ledkov |
systemd (Ubuntu Zesty): milestone |
|
zesty-updates |
|
2017-08-21 12:29:48 |
Dimitri John Ledkov |
systemd (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
2017-08-31 10:16:56 |
Dimitri John Ledkov |
systemd (Ubuntu Zesty): status |
Triaged |
In Progress |
|
2017-09-04 10:53:14 |
Dimitri John Ledkov |
description |
Context: fresh install of zesty via
debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1 http://fr.archive.ubuntu.com/ubuntu
ran via asystemd-nspawn with a static IP
1. Upon first connexion, a ping fails:
root@zesty1:~# ping google.com
ping: google.com: Temporary failure in name resolution
2. The content of /etc/resolv.conf:
root@zesty1:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
3. When running systemd-resolve --status:
root@zesty1:~# systemd-resolve --status
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::8888
2001:4860:4860::8844
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
(...)
4. After running this command the resolution is miraculously restored:
root@zesty1:~# ping google.com
PING google.com (172.217.22.142) 56(84) bytes of data.
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms |
[Impact]
systemd-resolved is not enabled by default, therefore relies on dbus activation to become active and operatable and update resolvconf with resolved stub resolver
[Fix]
Enable systemd-resolved in the src:systemd package by default, even when libnss-resolve is not installed
[Regression Potential]
Minimal, simply the service is now started earlier in the boot, as part of the multi-user.targer, rather than awaiting for dbus activation from command line tool or the nss-resolved module.
[Testcase]
Debootstrap minimal zesty, without libnss-resolve package installed, boot and check that 127.0.0.53 is present in /etc/resolv.conf and that systemd-resolved.service is running
Context: fresh install of zesty via
debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1 http://fr.archive.ubuntu.com/ubuntu
ran via asystemd-nspawn with a static IP
1. Upon first connexion, a ping fails:
root@zesty1:~# ping google.com
ping: google.com: Temporary failure in name resolution
2. The content of /etc/resolv.conf:
root@zesty1:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
3. When running systemd-resolve --status:
root@zesty1:~# systemd-resolve --status
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::8888
2001:4860:4860::8844
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
(...)
4. After running this command the resolution is miraculously restored:
root@zesty1:~# ping google.com
PING google.com (172.217.22.142) 56(84) bytes of data.
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms
64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms |
|
2017-09-07 18:05:13 |
Brian Murray |
systemd (Ubuntu Zesty): status |
In Progress |
Fix Committed |
|
2017-09-07 18:05:16 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2017-09-07 18:05:17 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
2017-09-07 18:05:21 |
Brian Murray |
tags |
|
verification-needed verification-needed-zesty |
|
2017-10-02 14:41:19 |
Dimitri John Ledkov |
tags |
verification-needed verification-needed-zesty |
verification-failed verification-failed-zesty |
|
2017-10-05 17:32:07 |
Brian Murray |
tags |
verification-failed verification-failed-zesty |
verification-needed verification-needed-zesty |
|
2017-10-10 07:50:43 |
Dimitri John Ledkov |
tags |
verification-needed verification-needed-zesty |
verification-done verification-done-zesty |
|
2017-10-26 14:28:26 |
Launchpad Janitor |
systemd (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
2017-10-26 14:29:03 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|