based on comment 29, and the assumption that the referenced upstream
commit does actually 'fix' (or at least work around) this, marking as
Fix Released for h and later.
** Description changed:
+ [impact]
+
+ on boot of a specific azure instance, the ID_NET_DRIVER parameter of the
+ instance's eth0 interface is not set. That leads to a failure of
+ systemd-networkd to take control of the interface after a restart of
+ systemd-networkd, which results in DNS failures (at first) and
+ eventually complete loss of networking (once the DHCP lease expires).
+
+ [test case]
+
+ this occurs on first boot of an instance using the specific image; it is
+ not reproducable using the latest ubuntu image nor any reboot of the
+ affected image, and it has not been reproducable (for me) when using
+ debug-enabled images based on the affected image.
+
+ So, while the problem is reproducable using the specific image in
+ question, it's not possible to verify the fix since any change to the
+ image removes reproducability.
+
+ [regression potential]
+
+ any regression would likely involve problems with systemd-udevd
+ processing 'change' events from network devices, and/or incorrect udevd
+ device properties.
+
+ [scope]
+
+ this is needed only for focal and groovy.
+
+ this is fixed by upstream commit e0e789c1e97 which is first included in
+ v247, so this is fixed already in hirsute.
+
+ while this commit is not included in bionic, due to the difficult nature
+ of reproducing (and verifying) this, and the fact it has only been seen
+ once on a focal image, I don't think it's appropriate to SRU to bionic
+ at this point; possibly it may be appropriate if this is ever reproduced
+ with a bionic image.
+
+ [other info]
+
+ note that this bug's subject and description, as well as the upstream
+ systemd bug subject and description, talk about the problem being DNS
+ resolution. However that is strictly a side-effect of the real problem
+ and is not the actual issue.
+
+ [original description]
+
The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to have
broken DNS resolution across much of our Azure fleet earlier today. We
ended up mitigating this by forcing reboots on the associated instances,
no combination of networkctl reload, reconfigure, systemctl daemon-
reexec, systemctl daemon-reload, netplan generate, netplan apply would
get resolvectl to have a DNS server again. The main symptom appears to
have been systemd-networkd believing it wasn't managing the eth0
interfaces:
ubuntu@machine-1:~$ sudo networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether routable unmanaged
2
links listed.
Which eventually made them lose their DNS resolvers:
ubuntu@machine-1:~$ sudo resolvectl dns
Global:
Link 2 (eth0):
After rebooting, we see this behaving properly:
ubuntu@machine-1:~$ sudo networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether routable configured
2 links listed.
ubuntu@machine-1:~$ sudo resolvectl dns
Global:
Link 2 (eth0): 168.63.129.16
This appears to be specifically linked to the upgrade, i.e. we were able to
provoke the issue by upgrading the systemd package, so I suspect it's part of
the packaging in the upgrade process.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
Lspci-vt:
-[0000:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(AGP disabled)
+-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA
+-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE
+-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI
\-08.0 Microsoft Corporation Hyper-V virtual VGA
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
Package: systemd 245.4-4ubuntu3.3
PackageArchitecture: amd64
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure
root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 panic=-1
ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65
Tags: focal uec-images
Uname: Linux 5.4.0-1031-azure x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090008
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
** Changed in: systemd (Ubuntu)
Status: Incomplete => Opinion
** Changed in: systemd (Ubuntu)
Status: Opinion => New
** Also affects: cloud-init (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Groovy)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902960
Title:
Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
resolution in some cases
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1902960/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
