| 2016-05-05 14:31:03 |
Martin Pitt |
bug |
|
|
added bug |
| 2016-05-05 14:31:14 |
Martin Pitt |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-05-05 14:31:14 |
Martin Pitt |
bug task added |
|
systemd (Ubuntu Yakkety) |
|
| 2016-05-05 14:31:14 |
Martin Pitt |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-05-05 14:31:14 |
Martin Pitt |
bug task added |
|
systemd (Ubuntu Xenial) |
|
| 2016-05-05 14:31:24 |
Martin Pitt |
systemd (Ubuntu Yakkety): status |
New |
Triaged |
|
| 2016-05-05 14:31:26 |
Martin Pitt |
systemd (Ubuntu Xenial): status |
New |
Triaged |
|
| 2016-05-05 14:31:29 |
Martin Pitt |
systemd (Ubuntu Yakkety): assignee |
|
Martin Pitt (pitti) |
|
| 2016-05-05 14:31:51 |
Martin Pitt |
bug |
|
|
added subscriber Christian Reis |
| 2016-05-05 19:11:33 |
Martin Pitt |
systemd (Ubuntu Yakkety): status |
Triaged |
Fix Committed |
|
| 2016-05-05 19:14:27 |
Martin Pitt |
systemd (Ubuntu Xenial): assignee |
|
Martin Pitt (pitti) |
|
| 2016-05-09 19:34:58 |
Martin Pitt |
systemd (Ubuntu Xenial): status |
Triaged |
In Progress |
|
| 2016-05-09 19:46:10 |
Martin Pitt |
description |
Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a DHCP exit hook for timesyncd to update the timesyncd configuration in /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up NTP servers, and restart timesyncd. |
Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a DHCP exit hook for timesyncd to update the timesyncd configuration in /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up NTP servers, and restart timesyncd.
SRU INFORMATION
===============
Rationale: This is a regression compared to trusty where we used ntpdate; /etc/dhcp/dhclient-exit-hooks.d/ntpdate ran ntpdate on the new NTP servers. This causes timesyncd to always try and talk to the disto configured server (ntp.ubuntu.com) which might be disallowed by firewall rules or other networking policy. Thus machines in such an environment never get a correct time sync even when they get a local NTP server advertised over DHCP.
Test case:
- Set up a DHCP server that includes NTP information. For example, you can set LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf in /etc/default/lxc-net, and create /etc/lxc/dnsmasq.conf with "dhcp-option=option:ntp-server,4.3.2.1", and then run QEMU on lxcbr0 instead of the builtin network.
- In the client machine, disconnect and reconnect the network (e. g. "sudo ifdown ens3; sudo ifup ens3").
- Check in "systemctl status systemd-timesyncd" that timesyncd tries to sync with the given NTP server (for the bogus 4.3.2.1 it will fail, but the point is that it did try).
Regression potential: A broken dhclient-exit-hooks.d has the potential to break subsequent hooks. dhclient-scripts runs the hooks without "set -e", but syntax errors can still cause damage. Thus it should be verified that later hooks (e. g. /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd) still run. Beyond that there is little potential for regression as |
|
| 2016-05-09 19:46:14 |
Martin Pitt |
systemd (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2016-05-09 19:46:16 |
Martin Pitt |
systemd (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-05-09 19:46:58 |
Martin Pitt |
summary |
create DHCP exit hook for setting NTP servers |
create DHCP exit hook for setting NTP servers through dhclient |
|
| 2016-05-09 19:47:23 |
Martin Pitt |
description |
Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a DHCP exit hook for timesyncd to update the timesyncd configuration in /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up NTP servers, and restart timesyncd.
SRU INFORMATION
===============
Rationale: This is a regression compared to trusty where we used ntpdate; /etc/dhcp/dhclient-exit-hooks.d/ntpdate ran ntpdate on the new NTP servers. This causes timesyncd to always try and talk to the disto configured server (ntp.ubuntu.com) which might be disallowed by firewall rules or other networking policy. Thus machines in such an environment never get a correct time sync even when they get a local NTP server advertised over DHCP.
Test case:
- Set up a DHCP server that includes NTP information. For example, you can set LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf in /etc/default/lxc-net, and create /etc/lxc/dnsmasq.conf with "dhcp-option=option:ntp-server,4.3.2.1", and then run QEMU on lxcbr0 instead of the builtin network.
- In the client machine, disconnect and reconnect the network (e. g. "sudo ifdown ens3; sudo ifup ens3").
- Check in "systemctl status systemd-timesyncd" that timesyncd tries to sync with the given NTP server (for the bogus 4.3.2.1 it will fail, but the point is that it did try).
Regression potential: A broken dhclient-exit-hooks.d has the potential to break subsequent hooks. dhclient-scripts runs the hooks without "set -e", but syntax errors can still cause damage. Thus it should be verified that later hooks (e. g. /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd) still run. Beyond that there is little potential for regression as |
Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a DHCP exit hook for timesyncd to update the timesyncd configuration in /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up NTP servers, and restart timesyncd.
SRU INFORMATION
===============
Rationale: This is a regression compared to trusty where we used ntpdate; /etc/dhcp/dhclient-exit-hooks.d/ntpdate ran ntpdate on the new NTP servers. This causes timesyncd to always try and talk to the disto configured server (ntp.ubuntu.com) which might be disallowed by firewall rules or other networking policy. Thus machines in such an environment never get a correct time sync even when they get a local NTP server advertised over DHCP (unless they use systemd-networkd, which is not done by default in Xenial).
Test case:
- Set up a DHCP server that includes NTP information. For example, you can set LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf in /etc/default/lxc-net, and create /etc/lxc/dnsmasq.conf with "dhcp-option=option:ntp-server,4.3.2.1", and then run QEMU on lxcbr0 instead of the builtin network.
- In the client machine, disconnect and reconnect the network (e. g. "sudo ifdown ens3; sudo ifup ens3").
- Check in "systemctl status systemd-timesyncd" that timesyncd tries to sync with the given NTP server (for the bogus 4.3.2.1 it will fail, but the point is that it did try).
Regression potential: A broken dhclient-exit-hooks.d has the potential to break subsequent hooks. dhclient-scripts runs the hooks without "set -e", but syntax errors can still cause damage. Thus it should be verified that later hooks (e. g. /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd) still run. Beyond that there is little potential for regression as |
|
| 2016-05-12 09:11:01 |
Adam Conrad |
systemd (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-05-12 09:11:03 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-05-12 09:11:04 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2016-05-12 09:11:09 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2016-05-12 15:43:17 |
Launchpad Janitor |
systemd (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2016-05-17 19:51:13 |
Martin Pitt |
description |
Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a DHCP exit hook for timesyncd to update the timesyncd configuration in /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up NTP servers, and restart timesyncd.
SRU INFORMATION
===============
Rationale: This is a regression compared to trusty where we used ntpdate; /etc/dhcp/dhclient-exit-hooks.d/ntpdate ran ntpdate on the new NTP servers. This causes timesyncd to always try and talk to the disto configured server (ntp.ubuntu.com) which might be disallowed by firewall rules or other networking policy. Thus machines in such an environment never get a correct time sync even when they get a local NTP server advertised over DHCP (unless they use systemd-networkd, which is not done by default in Xenial).
Test case:
- Set up a DHCP server that includes NTP information. For example, you can set LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf in /etc/default/lxc-net, and create /etc/lxc/dnsmasq.conf with "dhcp-option=option:ntp-server,4.3.2.1", and then run QEMU on lxcbr0 instead of the builtin network.
- In the client machine, disconnect and reconnect the network (e. g. "sudo ifdown ens3; sudo ifup ens3").
- Check in "systemctl status systemd-timesyncd" that timesyncd tries to sync with the given NTP server (for the bogus 4.3.2.1 it will fail, but the point is that it did try).
Regression potential: A broken dhclient-exit-hooks.d has the potential to break subsequent hooks. dhclient-scripts runs the hooks without "set -e", but syntax errors can still cause damage. Thus it should be verified that later hooks (e. g. /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd) still run. Beyond that there is little potential for regression as |
Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a DHCP exit hook for timesyncd to update the timesyncd configuration in /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up NTP servers, and restart timesyncd.
SRU INFORMATION
===============
Rationale: This is a regression compared to trusty where we used ntpdate; /etc/dhcp/dhclient-exit-hooks.d/ntpdate ran ntpdate on the new NTP servers. This causes timesyncd to always try and talk to the disto configured server (ntp.ubuntu.com) which might be disallowed by firewall rules or other networking policy. Thus machines in such an environment never get a correct time sync even when they get a local NTP server advertised over DHCP (unless they use systemd-networkd, which is not done by default in Xenial).
Test case:
- Set up a DHCP server that includes NTP information. For example, you can set LXC_DHCP_CONFILE=/etc/lxc/dnsmasq.conf in /etc/default/lxc-net, and create /etc/lxc/dnsmasq.conf with "dhcp-option=option:ntp-server,4.3.2.1", restart lxc-net, and then run QEMU on lxcbr0 instead of the builtin network.
- In the client machine, disconnect and reconnect the network (e. g. "sudo ifdown ens3; sudo ifup ens3").
- Check in "systemctl status systemd-timesyncd" that timesyncd tries to sync with the given NTP server (for the bogus 4.3.2.1 it will fail, but the point is that it did try).
Regression potential: A broken dhclient-exit-hooks.d has the potential to break subsequent hooks. dhclient-scripts runs the hooks without "set -e", but syntax errors can still cause damage. Thus it should be verified that later hooks (e. g. /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd) still run. Beyond that there is little potential for regression as |
|
| 2016-05-17 19:56:21 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
| 2016-05-23 06:58:42 |
Launchpad Janitor |
systemd (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-05-23 06:58:54 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-05-23 22:51:18 |
Nobuto Murata |
bug |
|
|
added subscriber Nobuto Murata |
