systemd-resolved configures no Current Scopes on start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Won't Fix
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
isc-dhcp (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Impish |
Won't Fix
|
Low
|
Unassigned | ||
Jammy |
Triaged
|
Low
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Running groovy on the desktop, with the systemd packages that migrated today(/overnight EDT).
# Steps to reproduce:
1) `systemctl restart systemd-
(This is a minimal reproducer, but I first saw this after an apt upgrade of systemd.)
# Expected behaviour:
DNS continues to work, status looks like this:
Link 2 (enp5s0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: ~.
# Actual behaviour:
DNS is unconfigured:
Link 2 (enp5s0)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
# Workaround
Disconnecting and reconnecting my network connection restored DNS functionality.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: systemd 246.5-1ubuntu1
ProcVersionSign
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: i3
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Wed Sep 23 09:05:42 2020
InstallationDate: Installed on 2019-05-07 (504 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
ProcKernelCmdLine: BOOT_IMAGE=
RebootRequiredPkgs: gnome-shell
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
2 overridden configuration files found.
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
Unit \xe2\x97\
------
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
Unit \xe2\x97\
UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago)
dmi.bios.date: 01/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.
dmi.board.name: B450M DS3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: Default string
dmi.product.name: B450M DS3H
dmi.product.sku: Default string
dmi.product.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Changed in ifupdown (Ubuntu): | |
status: | New → In Progress |
Changed in isc-dhcp (Ubuntu): | |
status: | New → Triaged |
tags: | added: rls-jj-incoming |
Changed in isc-dhcp (Ubuntu): | |
importance: | Undecided → High |
Changed in systemd (Ubuntu): | |
importance: | Undecided → High |
tags: | added: fr-2319 |
Changed in ifupdown (Ubuntu Jammy): | |
status: | New → Fix Released |
Changed in isc-dhcp (Ubuntu Jammy): | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | removed: rls-jj-incoming |
I haven't been able to reproduce in a lxd container or an EC2 instance; I don't have a convenient way of testing a different NetworkManager system, unfortunately.