[Bug 2097769] Re: Installation of ubuntu-desktop-minimal breaks DNS

[James McKenzie]

I've attached the output of `journalctl -u systemd-networkd -u
NetworkManager -b`

Just FYI, this is taken from a fresh VM with a basically default Ubuntu Server 24.04 installation after installing ubuntu-desktop-minimal.
I had to push some workarounds in our production deployment and I encountered a new/separate bug affecting netplan config so it's just easier to reproduce in a clean VM. The primary issue remains.

Running `nmcli device status` gives the below:
ebiadmin at test24:~$ nmcli dev status
DEVICE  TYPE      STATE                   CONNECTION 
lo      loopback  connected (externally)  lo         
enp1s0  ethernet  unmanaged               -- 


> PS: I guess the expectation here would be for systemd-networkd to keep managing the network+DNS (which it doesn't for some reason), until reboot or "netplan apply" is executed. Is that how it worked on 22.04?

Yes this is how it worked on 22.04. networkd maintained network+DNS
until next reboot as long as "netplan apply" isn't executed.

** Attachment added: "network.journal"
   https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2097769/+attachment/5857420/+files/network.journal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2097769

Title:
  Installation of ubuntu-desktop-minimal breaks DNS

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After performing an autoinstall with Ubuntu Server ISO and rebooting,
  trying to automate the installation of ubuntu-desktop-minimal causes
  DNS settings to be lost.

  For our specific use-case, we are installing ubuntu server (fully automated), then using Puppet to install desktop packages. This was working without any manual interaction previously on both Ubuntu 22.04 and 24.04
  For the last week or so, deployments of 24.04 (22.04 is still fine) are getting stuck after installing ubuntu-desktop-minimal. The DNS server settings are lost, but IP connectivity remains.

  
  Step-by-step
  1) Install Ubuntu Server with default network configuration using autoinstall.
  2) Reboot and install network-manager (note that everything is still working normally)
  3) Install ubuntu-desktop-minimal

  DNS settings are now lost on the primary interface, yet IP
  connectivity remains. networkd is still managing the interface, but
  "netplan get" reports that NetworkManager is the current renderer.

  ```
  network:
    version: 2
    renderer: NetworkManager
    ethernets:
      enp1s0:
        critical: true
        nameservers:
          addresses:
          - 172.16.1.100
          - 172.18.1.100
        dhcp-identifier: "mac"
        dhcp4: true
  ```

  
  We can workaround the problem forcing an extra reboot after installing ubuntu-desktop-minimal. But previously this workflow was fine without rebooting until the very end of the config.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.4-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
  Uname: Linux 6.8.0-52-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Mon Feb 10 10:47:43 2025
  InstallationDate: Installed on 2025-02-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware7,1
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-52-generic root=/dev/mapper/vg00-root ro
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  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\x8f.service could not be found.
   ------
   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\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2021
  dmi.bios.vendor: VMware, Inc.
  dmi.bios.version: VMW71.00V.18227214.B64.2106252220
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.18227214.B64.2106252220:bd06/25/2021:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware7,1
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2097769/+subscriptions