systemd-resolved constantly restarts on Bionic upgraded from Xenial
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | systemd (Ubuntu) |
Low
|
Unassigned | ||
| | Bionic |
Medium
|
Louis Bouchard | ||
| | Cosmic |
Undecided
|
Unassigned | ||
| | Disco |
Low
|
Unassigned | ||
| | Eoan |
Undecided
|
Unassigned | ||
| | Focal |
Low
|
Unassigned | ||
Bug Description
[Impact]
Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state?
Application that require Name Resolution may fail while the service is being unnecessarily restarted
[Test case]
(1) Append make_resolv_conf to the end of the file, so it gets executed
(2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example:
sudo new_domain_
sudo new_domain_
=> no restart
sudo new_domain_
=> should restart
sudo new_domain_
=> no restart
sudo new_domain_
=> should restart
[Regression potential]
The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent.
[other info]
this fix was included in the initial release of systemd for eoan, but the fix required the additional change in bug 1849608. Both the original patch plus that change (to avoid using bash-specific &>) are included in the b/d patch for this bug.
[Original bug report]
If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon
Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105
Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
Nov 26 16:59:41 srv-qvjhx systemd-
Nov 26 16:59:41 srv-qvjhx systemd-
Nov 26 16:59:41 srv-qvjhx systemd-
Nov 26 16:59:41 srv-qvjhx systemd-
Nov 26 16:59:41 srv-qvjhx systemd-
Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-
Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds.
Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 4.4.0-139-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
Date: Mon Nov 26 16:17:52 2018
PackageArchitec
SourcePackage: ubuntu-
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Dimitri John Ledkov: Pending requested 2018-12-17
-
Diff: 27 lines (+9/-1)1 file modifieddebian/extra/dhclient-enter-resolved-hook (+9/-1)
- Dimitri John Ledkov: Pending requested 2018-12-17
-
Diff: 210 lines (+127/-2) (has conflicts)5 files modifieddebian/changelog (+70/-0)
debian/extra/dhclient-enter-resolved-hook (+9/-1)
debian/gbp.conf (+1/-1)
debian/patches/meson-rename-Ddebug-to-Ddebug-extra.patch (+41/-0)
debian/patches/series (+6/-0)
| Neil Wilson (neil-aldur) wrote : | #1 |
| summary: |
- systems-resolved constantly restarts on Bionic upgraded from Xenial + systemd-resolved constantly restarts on Bionic upgraded from Xenial |
| tags: | added: id-5c0011e969ed904c67dda9ee |
| Julian Andres Klode (juliank) wrote : | #2 |
| Julian Andres Klode (juliank) wrote : | #3 |
The dbus API is only available in 239, which means we can't use it in bionic.
We could maybe make the hook just restart resolved if the new files it wrote are different from the old files.
| Julian Andres Klode (juliank) wrote : | #4 |
Ah no, 229, not 239 it seems.
| no longer affects: | ubuntu-release-upgrader (Ubuntu) |
| Changed in systemd (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Neil Wilson (neil-aldur) wrote : | #5 |
I think just a delta change process would be fine. It's restarting when there is no change in lease details, and just clogging up the logs.
btw I am not suggesting leaving dhclient there is a bug - hence the title of the bug.
| Julian Andres Klode (juliank) wrote : | #6 |
Here's a patch while the git branch is pushing.
| Changed in systemd (Ubuntu): | |
| status: | Triaged → In Progress |
| Julian Andres Klode (juliank) wrote : | #7 |
If we want to backport this to stable releases, we need a test case. What I came up with, as I was not able to simulate dhcp lease refreshes, is:
(1) Append make_resolv_conf to the end of the file, so it gets executed
(2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change.
| description: | updated |
| description: | updated |
| tags: | added: patch |
| dat (dat-1982) wrote : | #8 |
@juliank
I *believe* this is impacting our AWS ubuntu EC2 machines and causing wild DNS errors impacting our users, I tried to apply the patch in this thread but it doesn't work, it complains like this
/etc/
about this line
if ! cmp --quiet $oldstate <(md5sum $statedir/
Also for me this line
+ md5sum $statedir/
outputs to stdout
$ sudo dhclient
RTNETLINK answers: File exists
d41d8cd98f00
md5sum: /run/systemd/
and the resulting temp file is empty.
Dunno why your patch misbehaves like this but I really have no time to investigate further.
I've attached a patch that seems to be working on our servers in case others are experiencing the same issue and need a quick fix.
----
Adding few server details in case you need 'em:
$ uname -a
Linux ip-172-31-14-255 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
$ dhclient --version
isc-dhclient-4.3.5
$ systemd --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-
$ bash --version
GNU bash, version 4.4.19(1)-release (x86_64-
| dat (dat-1982) wrote : | #9 |
been running for 1 hour, seems to be working as expected
finally got one minute to create a patch against systemd repo instead of a live server
| Changed in systemd (Ubuntu Bionic): | |
| status: | New → Confirmed |
| Changed in systemd (Ubuntu Cosmic): | |
| status: | New → Confirmed |
| Changed in systemd (Ubuntu Disco): | |
| status: | In Progress → Confirmed |
xnox, it looks like you're missing a "$" in md5sum command from:
https:/
for the -proposed systemd version:
/sbin/dhclient-
Adding it solved my boot problem (systemd stucks in networking services).
cheers o/
| Dimitri John Ledkov (xnox) wrote : Re: [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial | #11 |
Lol
On Thu, 30 May 2019, 20:20 Rafael David Tinoco, <
<email address hidden>> wrote:
> xnox, it looks like you're missing a "$" in md5sum command from:
>
>
> https:/
>
> for the -proposed systemd version:
>
> /sbin/dhclient-
> Syntax error: "(" unexpected
>
> Adding it solved my boot problem (systemd stucks in networking
> services).
>
> cheers o/
>
> --
> You received this bug notification because you are subscribed to systemd
> in Ubuntu.
> Matching subscriptions: systemd
> https:/
>
> Title:
> systemd-resolved constantly restarts on Bionic upgraded from Xenial
>
> To manage notifications about this bug go to:
>
> https:/
>
| Launchpad Janitor (janitor) wrote : | #12 |
This bug was fixed in the package systemd - 240-6ubuntu9
---------------
systemd (240-6ubuntu9) eoan; urgency=medium
* Fix typpo in storage test.
File: debian/
https:/
* Fix bashism
File: debian/
https:/
systemd (240-6ubuntu8) eoan; urgency=medium
* Only restart resolved on changes in dhclient enter hook.
This prevents spurious restarts of resolved on rebounds when
the addresses did not change. (LP: #1805183)
Author: Julian Andres Klode
File: debian/
https:/
* Wait for cryptsetup unit to start, before stopping.
Patch from cascardo. Plus small refactor for readability. (LP: #1814373)
File: debian/
https:/
* Wait for systemctl is-system-running state.
File: debian/
https:/
systemd (240-6ubuntu7) eoan; urgency=medium
* Revert "Add check to switch VTs only between K_XLATE or K_UNICODE"
This reverts commit 60407728a1a4531
Files:
- debian/
- debian/
https:/
* Cherrypick missing systemd-stable patches to unbreak wireguard peer endpoints.
Signed-off-by: Dimitri John Ledkov <email address hidden> (LP: #1825378)
Author: Dan Streetman
Files:
- debian/
- debian/
- debian/
- debian/
https:/
* Remove expected failure from passing test.
Signed-off-by: Dimitri John Ledkov <email address hidden> (LP: #1829450)
Author: Dan Streetman
File: debian/
https:/
* Fix false negative checking for running jobs after boot.
Signed-off-by: Dimitri John Ledkov <email address hidden> (LP: #1825997)
Author: Dan Streetman
File: debian/
https:/
* Cherrypick ask-password: prevent buffer ...
| Changed in systemd (Ubuntu): | |
| status: | Confirmed → Fix Released |
| Changed in systemd (Ubuntu Bionic): | |
| importance: | Undecided → Medium |
| assignee: | nobody → Louis Bouchard (louis) |
| status: | Confirmed → In Progress |
| Louis Bouchard (louis) wrote : | #13 |
For Info, I'm repearing an SRU upload for Bionic hopefully available by End Of Day
| description: | updated |
| tf8 (tifeit) wrote : | #14 |
This still looks like an issue in Ubuntu 18.04 LTS. At least on systems that was upgraded from 14.04 release. I will disable systemd-resolved and revert to good old resolv.conf but what is the actual recommended workaround while the fix is not released?
| dat (dat-1982) wrote : | #15 |
@tf8 the patch in https:/
| Steve Langasek (vorlon) wrote : | #16 |
+ md5sum $statedir/
"&>" is a bashism. /sbin/dhclient-
$ dash
$ echo foo &> output
foo
$ cat output
[1] + Done echo foo
$ ^D
$
An upload of systemd to bionic-proposed has been rejected from the upload queue for the following reason: "wrong use of bashisms in shell script, does not work as intended".
| Changed in systemd (Ubuntu Cosmic): | |
| status: | Confirmed → Won't Fix |
| Steve Langasek (vorlon) wrote : | #18 |
This was also pointed out specifically in comment #8.
I'm reopening the trunk task on this bug as well since the bug is still there in eoan.
| Changed in systemd (Ubuntu): | |
| status: | Fix Released → Triaged |
| dat (dat-1982) wrote : | #19 |
Steve in comment #9 I left a patch against the repo that iirc was working fine on my machines. Maybe it can be helpful. Thanks
| Louis Bouchard (louis) wrote : | #20 |
Ok, I'll have a look at it; I only backported the Eoan fix to Bionic
| Ivan Brawley (brawley) wrote : | #21 |
I've found the patch applied to Eoan was the broken version where it used the bash'ism instead of the much more basic (and more portable) sh'ism of redirecting both STDOUT and STDERR.
I have confirmed this behaviour in Eoan (see bug #1850009) after doing an upgrade to this release.
I did a quick fix patch that is basically the same as #9 (I redirect only STDOUT however where as #9 redirects both STDOUT and STDERR).
| Changed in systemd (Ubuntu Eoan): | |
| status: | New → Fix Released |
| Changed in systemd (Ubuntu Focal): | |
| status: | Triaged → Fix Released |
| description: | updated |
| Steve Langasek (vorlon) wrote : | #22 |
This has been wrongly marked as fixed in eoan. It's not; the fix for this is still in eoan-proposed in systemd 242-7ubuntu3.2. I don't know why the separate bug LP: #1849608 was used for that SRU vs this one. Maybe the argument is that in eoan, systemd-resolved is *never* restarted, instead of being *always* restarted? But I think they should be treated as the same bug.
| Changed in systemd (Ubuntu Eoan): | |
| status: | Fix Released → Triaged |
| status: | Triaged → Fix Committed |
Hello Neil, or anyone else affected,
Accepted systemd into disco-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
| Changed in systemd (Ubuntu Disco): | |
| status: | Confirmed → Fix Committed |
| tags: | added: verification-needed verification-needed-disco |
All autopkgtests for the newly accepted systemd (240-6ubuntu5.8) for disco have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-
php7.2/
gvfs/1.
pdns-recursor/
webhook/unknown (armhf)
munin/2.
systemd/
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
| Steven Shiau (stevenshiau) wrote : | #25 |
I have tested Ubuntu Focal with systemd 243-3ubuntu1:
https:/
and the issue I have reported in Bug 1849608, which is marked as the duplicate of this bug, is gone now. Hence I confirmed the fix works here.
Hello Neil, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
| Changed in systemd (Ubuntu Bionic): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed-bionic |
| Dan Streetman (ddstreet) wrote : | #27 |
with dnsmasq server setup to provide dhcp with 1m lease timeout, just run dhclient on test system:
ubuntu@
ii systemd 240-6ubuntu5.7 amd64 system and service manager
ubuntu@
Nov 14 16:02:12 lp1805183-d systemd[1]: Started Network Name Resolution.
ubuntu@
ubuntu@
Nov 14 16:02:12 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:04:32 lp1805183-d systemd[1]: Started Network Name Resolution.
ubuntu@
Nov 14 16:02:12 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:04:32 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:05:22 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:06:11 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:06:57 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:07:52 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:08:41 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:09:25 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:10:17 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:11:03 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:11:51 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:12:33 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:13:24 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:14:16 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:15:11 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:16:03 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:16:46 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:17:34 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:18:23 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:19:16 lp1805183-d systemd[1]: Started Network Name Resolution.
ubuntu@
ii systemd 240-6ubuntu5.8 amd64 system and service manager
ubuntu@
Nov 14 16:21:20 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:29:41 lp1805183-d systemd[1]: Started Network Name Resolution.
ubuntu@
cmp: EOF on /tmp/tmp.qY6fTBCaSb which is empty
ubuntu@
Nov 14 16:21:20 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:29:41 lp1805183-d systemd[1]: Started Network Name Resolution.
Nov 14 16:30:51 lp1805183-d systemd[1]: Started Network Name Resolution.
| tags: |
added: verification-done-disco removed: verification-needed-disco |
| Neil Wilson (neil-aldur) wrote : | #28 |
LGTM on bionic
ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii
ii systemd 237-3ubuntu10.32 i386 system and service manager
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44 srv-ywz63 systemd[1]: Started Network Name Resolution.
ubuntu@srv-ywz63:~$ sudo dhclient eth0
RTNETLINK answers: File exists
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44 srv-ywz63 systemd[1]: Started Network Name Resolution.
ubuntu@srv-ywz63:~$
| tags: |
added: verification-done-bionic removed: verification-needed-bionic |
| Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (systemd/237-3ubuntu10.32) | #29 |
All autopkgtests for the newly accepted systemd (237-3ubuntu10.32) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.
linux/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
| Dan Streetman (ddstreet) wrote : | #30 |
> ubuntu@srv-ywz63:~$ sudo dhclient eth0
> RTNETLINK answers: File exists
I think you're trying to start dhclient on an interface that's already setup.
root@lp1805183-b:~# dpkg -l systemd|grep ii
ii systemd 237-3ubuntu10.31 amd64 system and service manager
root@lp1805183-b:~# journalctl -b -u systemd-resolved | grep Started
Nov 15 12:38:54 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# dhclient ens8
root@lp1805183-b:~# journalctl -b -u systemd-resolved | grep Started
Nov 15 12:38:54 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 12:45:42 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# sleep 300 ; journalctl -b -u systemd-resolved | grep Started
Nov 15 12:38:54 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 12:45:42 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 12:46:29 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 12:47:22 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 12:48:10 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 12:49:00 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 12:49:51 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# dpkg -l systemd|grep ii
ii systemd 237-3ubuntu10.32 amd64 system and service manager
root@lp1805183-b:~# journalctl -b -u systemd-resolved | grep Started
Nov 15 13:19:35 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# dhclient ens8
cmp: EOF on /tmp/tmp.64FqHLxW32 which is empty
root@lp1805183-b:~# sleep 300 ; journalctl -b -u systemd-resolved | grep Started
Nov 15 13:19:35 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 15 13:20:25 lp1805183-b systemd[1]: Started Network Name Resolution.
| tags: |
added: verification-done removed: verification-needed |
| Neil Wilson (neil-aldur) wrote : | #31 |
"I think you're trying to start dhclient on an interface that's already setup."
It just triggers a lease refresh on the existing interface, which has the same issue.
Nov 15 14:17:10 srv-ywz63 systemd-
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started Session 27 of user ubuntu.
Nov 15 14:17:30 srv-ywz63 sudo[12484]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=
Nov 15 14:17:30 srv-ywz63 sudo[12484]: pam_unix(
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: DHCPREQUEST of 10.241.196.178 on eth0 to 255.255.255.255 port 67 (xid=0x511efd40)
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: DHCPACK of 10.241.196.178 from 10.241.196.177
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: bound to 10.241.196.178 -- renewal in 1421 seconds.
Nov 15 14:17:30 srv-ywz63 sudo[12484]: pam_unix(
Hello Neil, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
| tags: |
added: verification-needed verification-needed-bionic removed: verification-done verification-done-bionic |
| Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (systemd/237-3ubuntu10.33) | #33 |
All autopkgtests for the newly accepted systemd (237-3ubuntu10.33) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.
dovecot/
umockdev/0.11.1-1 (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
| Launchpad Janitor (janitor) wrote : | #34 |
This bug was fixed in the package systemd - 240-6ubuntu5.8
---------------
systemd (240-6ubuntu5.8) disco; urgency=medium
[ Victor Tapia ]
* d/p/resolved_
Fix regression introduced by
resolved-
DNSSEC=yes (LP: #1796501)
[ Dan Streetman ]
* d/p/lp1840640-
allow sync_file_range2 in nspawn container (LP: #1840640)
* d/p/lp1847527-
do not request Content-Length if Transfer-Encoding is chunked
(LP: #1847527)
* d/t/storage: fix flaky test
(LP: #1847815)
* d/p/lp1843381-
debian/
fix rename delay for systems using "Dell MAC passthrough"
(LP: #1843381)
* d/p/lp1849733/
d/p/
ignore EDNS0 payload limit when responding over TCP (LP: #1849733)
* d/p/lp1849658-
- Fix bug in refcounting TCP stream types (LP: #1849658)
* d/extra/
- only restart resolved if dhclient conf changed (LP: #1805183)
[ Balint Reczey ]
* d/p/test-
fix test breakage due to running in nested lxd container
(LP: #1845337)
-- Dan Streetman <email address hidden> Fri, 04 Oct 2019 09:06:58 -0400
| Changed in systemd (Ubuntu Disco): | |
| status: | Fix Committed → Fix Released |
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
| Dan Streetman (ddstreet) wrote : | #36 |
root@lp1805183-b:~# dpkg -l systemd|grep ii
ii systemd 237-3ubuntu10.33 amd64 system and service manager
root@lp1805183-b:~# journalctl -b -u systemd-resolved | grep Started
Nov 26 03:04:30 lp1805183-b systemd[1]: Started Network Name Resolution.
root@lp1805183-b:~# dhclient ens8
cmp: EOF on /tmp/tmp.yJwQabpfMe which is empty
root@lp1805183-b:~# sleep 300 ; journalctl -b -u systemd-resolved | grep Started
Nov 26 03:04:30 lp1805183-b systemd[1]: Started Network Name Resolution.
Nov 26 03:06:06 lp1805183-b systemd[1]: Started Network Name Resolution.
| tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic |
| Launchpad Janitor (janitor) wrote : | #37 |
This bug was fixed in the package systemd - 237-3ubuntu10.33
---------------
systemd (237-3ubuntu10.33) bionic; urgency=medium
* d/p/lp1852754/
d/p/
d/p/
- Complete link setup after setting mtu (LP: #1852754)
systemd (237-3ubuntu10.32) bionic; urgency=medium
[ Victor Tapia ]
* d/p/resolved_
Fix regression introduced by
resolved-
DNSSEC=yes (LP: #1796501)
[ Dan Streetman ]
* d/p/fix-
- Fix typo in previous patch
* d/p/lp1840640-
- allow sync_file_range2 in nspawn container
(LP: #1840640)
* d/p/lp1783994-
- avoid systemd-
(LP: #1783994)
* d/p/lp1832672-
- do not fail entire file on error when parsing /etc/hosts
- parse # char anywhere in line as start of comment
(LP: #1832672)
* d/p/lp1843381-
debian/
- fix rename delay for systems using "Dell MAC passthrough"
(LP: #1843381)
* d/p/lp1849733/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
- add TCP pipelining to handle getaddrinfo() fallback to TCP
- ignore EDNS0 payload limit when responding over TCP (LP: #1849733)
* d/p/lp1849658-
- Fix bug in refcounting TCP stream types (LP: #1849658)
* d/p/lp1850704/
d/p/
- Fix setting mtu if interface already up (LP: #1850704)
* d/extra/
- only restart resolved if dhclient conf changed (LP: #1805183)
-- Dan Streetman <email address hidden> Fri, 15 Nov 2019 10:01:16 -0500
| Changed in systemd (Ubuntu Bionic): | |
| status: | Fix Committed → Fix Released |
| Changed in systemd (Ubuntu Eoan): | |
| status: | Fix Committed → Fix Released |
First of all, dhclient remaining in place is not a bug. Systems are not switching to netplan and networkd on upgrade.
The restart caused by /etc/dhcp/