| 2016-12-14 15:41:06 |
Ryan Harper |
bug |
|
|
added bug |
| 2016-12-14 15:42:04 |
Ryan Harper |
bug task added |
|
resolvconf (Ubuntu) |
|
| 2016-12-15 04:53:47 |
David Glasser |
bug |
|
|
added subscriber David Glasser |
| 2016-12-15 16:20:03 |
Ryan Harper |
attachment added |
|
xenial_resolvconf-lp1649931.diff https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4792030/+files/xenial_resolvconf-lp1649931.diff |
|
| 2016-12-15 16:27:13 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2016-12-15 16:27:19 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2016-12-15 19:42:13 |
Ryan Harper |
description |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug. |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug.
[SRU]
Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target.
Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial.
Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash
# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd
# enable networkd and netplan
apt install -y nplan
cat <<EOF > /etc/netplan/nplan.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true
EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
netplan generate
# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a After=systemd-network-wait-online.service' /lib/systemd/system/cloud-init.service
reboot
# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service
# the order should be:
1. resolvconf: systemd[1]: Started Nameserver information manager.
2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured...
3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS.
4. network-online.target: systemd[1]: Reached target Network is Online.
=== BAD OUTPUT ===
On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output:
Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS.
=== GOOD OUTPUT ===
On a passing system, Reached target Network is Online occurs after 1, 2, and 3.
Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS.
Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. |
|
| 2016-12-15 19:47:23 |
Ryan Harper |
attachment added |
|
xenial-dns-before-online-target-lp1649931.debdiff https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4792126/+files/xenial-dns-before-online-target-lp1649931.debdiff |
|
| 2016-12-15 21:27:31 |
Brian Murray |
resolvconf (Ubuntu): status |
New |
Incomplete |
|
| 2016-12-15 21:45:34 |
Ryan Harper |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440 |
|
| 2016-12-16 00:32:00 |
Brian Murray |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2016-12-16 00:32:19 |
Brian Murray |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-12-16 00:32:19 |
Brian Murray |
bug task added |
|
resolvconf (Ubuntu Xenial) |
|
| 2016-12-16 00:32:19 |
Brian Murray |
bug task added |
|
systemd (Ubuntu Xenial) |
|
| 2016-12-16 00:32:32 |
Brian Murray |
resolvconf (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2016-12-16 00:32:38 |
Brian Murray |
systemd (Ubuntu): status |
Fix Released |
New |
|
| 2016-12-16 02:35:00 |
Steve Langasek |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2016-12-16 02:38:57 |
Steve Langasek |
resolvconf (Ubuntu Yakkety): status |
New |
Fix Committed |
|
| 2016-12-16 02:44:29 |
Steve Langasek |
resolvconf (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-12-16 02:44:37 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-12-16 02:44:42 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2016-12-16 02:44:48 |
Steve Langasek |
tags |
patch |
patch verification-needed |
|
| 2016-12-16 02:45:14 |
Steve Langasek |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2016-12-17 17:01:45 |
Mathew Hodson |
bug task added |
|
resolvconf (Debian) |
|
| 2016-12-17 17:05:08 |
Mathew Hodson |
resolvconf (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-12-17 17:05:09 |
Mathew Hodson |
resolvconf (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2016-12-17 17:05:11 |
Mathew Hodson |
resolvconf (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2016-12-17 17:05:13 |
Mathew Hodson |
systemd (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-12-17 17:05:16 |
Mathew Hodson |
systemd (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2016-12-18 00:34:37 |
Bug Watch Updater |
resolvconf (Debian): status |
Unknown |
Fix Committed |
|
| 2017-01-13 12:34:44 |
Robie Basak |
systemd (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2017-01-18 21:02:22 |
Ryan Harper |
description |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug.
[SRU]
Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target.
Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial.
Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash
# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd
# enable networkd and netplan
apt install -y nplan
cat <<EOF > /etc/netplan/nplan.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true
EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
netplan generate
# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a After=systemd-network-wait-online.service' /lib/systemd/system/cloud-init.service
reboot
# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service
# the order should be:
1. resolvconf: systemd[1]: Started Nameserver information manager.
2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured...
3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS.
4. network-online.target: systemd[1]: Reached target Network is Online.
=== BAD OUTPUT ===
On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output:
Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS.
=== GOOD OUTPUT ===
On a passing system, Reached target Network is Online occurs after 1, 2, and 3.
Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS.
Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug.
[SRU]
Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target.
Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial.
Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash
# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd
# enable networkd and netplan
apt install -y nplan
cat <<EOF > /etc/netplan/nplan.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true
EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
netplan generate
# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a After=systemd-networkd-wait-online.service' /lib/systemd/system/cloud-init.service
reboot
# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service
# the order should be:
1. resolvconf: systemd[1]: Started Nameserver information manager.
2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured...
3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS.
4. network-online.target: systemd[1]: Reached target Network is Online.
=== BAD OUTPUT ===
On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output:
Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS.
=== GOOD OUTPUT ===
On a passing system, Reached target Network is Online occurs after 1, 2, and 3.
Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS.
Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. |
|
| 2017-01-18 21:36:57 |
Ryan Harper |
tags |
patch verification-needed |
patch verification-failed |
|
| 2017-01-28 19:41:54 |
Mathew Hodson |
bug |
|
|
added subscriber Mathew Hodson |
| 2017-02-03 15:42:25 |
Ryan Harper |
attachment added |
|
xenial-dns-before-online-target-lp1649931-v2.debdiff https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4812597/+files/xenial-dns-before-online-target-lp1649931-v2.debdiff |
|
| 2017-02-10 16:10:14 |
Scott Moser |
systemd (Ubuntu Xenial): status |
Fix Committed |
Confirmed |
|
| 2017-02-15 14:29:46 |
Chris J Arges |
systemd (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2017-02-15 14:29:56 |
Chris J Arges |
tags |
patch verification-failed |
patch |
|
| 2017-02-15 14:29:57 |
Chris J Arges |
tags |
patch |
patch verification-needed |
|
| 2017-02-15 18:37:17 |
Ryan Harper |
description |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug.
[SRU]
Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target.
Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial.
Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash
# make sure you're on systemd-229-4ubuntu13
apt update && apt install -y systemd
# enable networkd and netplan
apt install -y nplan
cat <<EOF > /etc/netplan/nplan.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true
EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
netplan generate
# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a After=systemd-networkd-wait-online.service' /lib/systemd/system/cloud-init.service
reboot
# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service
# the order should be:
1. resolvconf: systemd[1]: Started Nameserver information manager.
2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured...
3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS.
4. network-online.target: systemd[1]: Reached target Network is Online.
=== BAD OUTPUT ===
On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output:
Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS.
=== GOOD OUTPUT ===
On a passing system, Reached target Network is Online occurs after 1, 2, and 3.
Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS.
Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug.
[SRU]
Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target.
Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial.
Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash
# make sure you're on systemd-229-4ubuntu17
apt update && apt install -y systemd
# enable networkd and netplan
apt install -y nplan
cat <<EOF > /etc/netplan/nplan.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true
EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
netplan generate
# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a After=systemd-networkd-wait-online.service' /lib/systemd/system/cloud-init.service
reboot
# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service
# the order should be:
1. resolvconf: systemd[1]: Started Nameserver information manager.
2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured...
3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS.
4. network-online.target: systemd[1]: Reached target Network is Online.
=== BAD OUTPUT ===
On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output:
Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS.
=== GOOD OUTPUT ===
On a passing system, Reached target Network is Online occurs after 1, 2, and 3.
Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS.
Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. |
|
| 2017-02-16 03:05:04 |
paz |
bug |
|
|
added subscriber paz |
| 2017-02-21 21:39:25 |
Ryan Harper |
tags |
patch verification-needed |
patch verification-done |
|
| 2017-02-21 23:15:53 |
Brian Murray |
tags |
patch verification-done |
patch verification-done-xenial |
|
| 2017-03-02 01:10:03 |
Mathew Hodson |
removed subscriber Mathew Hodson |
|
|
|
| 2017-03-02 17:52:41 |
Launchpad Janitor |
resolvconf (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-03-02 17:52:46 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-03-06 19:30:02 |
Ryan Harper |
description |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug.
[SRU]
Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target.
Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial.
Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash
# make sure you're on systemd-229-4ubuntu17
apt update && apt install -y systemd
# enable networkd and netplan
apt install -y nplan
cat <<EOF > /etc/netplan/nplan.yaml
network:
version: 2
ethernets:
eth0:
dhcp4: true
EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
netplan generate
# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a After=systemd-networkd-wait-online.service' /lib/systemd/system/cloud-init.service
reboot
# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service
# the order should be:
1. resolvconf: systemd[1]: Started Nameserver information manager.
2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured...
3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS.
4. network-online.target: systemd[1]: Reached target Network is Online.
=== BAD OUTPUT ===
On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output:
Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS.
=== GOOD OUTPUT ===
On a passing system, Reached target Network is Online occurs after 1, 2, and 3.
Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS.
Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. |
Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug.
[SRU]
Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target.
Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial.
Test Case:
lxc launch ubuntu-daily:xenial x1
lxc exec x1 /bin/bash
# make sure you're on systemd-229-4ubuntu17
apt update && apt install -y systemd
# enable networkd and netplan
apt install -y nplan
cat <<EOF > /etc/netplan/nplan.yaml
network:
version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4: true
all-eth:
match:
name: "eth*"
dhcp4: true
EOF
sed -i.orig -e 's/^source/# source/' /etc/network/interfaces
netplan generate
# make sure cloud-init.service uses networkd
sed -i.orig -e '/After=networking.service/a After=systemd-networkd-wait-online.service' /lib/systemd/system/cloud-init.service
reboot
# check that the order of execution with:
journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service
# the order should be:
1. resolvconf: systemd[1]: Started Nameserver information manager.
2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured...
3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS.
4. network-online.target: systemd[1]: Reached target Network is Online.
=== BAD OUTPUT ===
On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output:
Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online.
Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS.
=== GOOD OUTPUT ===
On a passing system, Reached target Network is Online occurs after 1, 2, and 3.
Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager.
Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured...
Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo
Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured.
Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS...
Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS.
Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. |
|
| 2017-03-08 15:09:36 |
Brian Murray |
systemd (Ubuntu Xenial): status |
Fix Committed |
Incomplete |
|
| 2017-03-08 17:56:14 |
Ryan Harper |
attachment added |
|
lp1649931-release-network-matrix.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4833940/+files/lp1649931-release-network-matrix.txt |
|
| 2017-03-17 18:29:34 |
Steve Langasek |
systemd (Ubuntu Xenial): status |
Incomplete |
Fix Committed |
|
| 2017-04-20 07:51:27 |
Steve Langasek |
tags |
patch verification-done-xenial |
patch verification-done-xenial verification-done-yakkety |
|
| 2017-04-20 16:57:42 |
Launchpad Janitor |
resolvconf (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-04-27 22:59:38 |
Launchpad Janitor |
systemd (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2020-01-14 18:21:48 |
Bug Watch Updater |
resolvconf (Debian): status |
Fix Committed |
Fix Released |
|
