[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Wed Jun 26 07:40:02 UTC 2024

*** This bug is a duplicate of bug 2054761 ***
    https://bugs.launchpad.net/bugs/2054761

can not find local pc's since Ubuntu 22.0.4 to 24.04

sudo nano  /etc/nsswitch.conf

sudo nano /etc/mdns.allow
aio at aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio at aio:~$ ls -l /etc/systemd/system/systemd-resolved.service
ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file or directory
aio at aio:~$ sudo systemctl unmask systemd-resolved
aio at aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio at aio:~$ sudo dpkg-reconfigure resolvconf
dpkg-query: package 'resolvconf' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolvconf is not installed
aio at aio:~$ sudo apt install systemd-resolved
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
systemd-resolved is already the newest version (255.4-1ubuntu8.1).
systemd-resolved set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
aio at aio:~$ sudo dpkg-reconfigure resolvconf
dpkg-query: package 'resolvconf' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolvconf is not installed
aio at aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio at aio:~$ sudo apt install systemd-resolved
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
systemd-resolved is already the newest version (255.4-1ubuntu8.1).
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
aio at aio:~$ sudo apt install --reinstall systemd-resolved
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 33 not upgraded.
Need to get 0 B/296 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 838554 files and directories currently installed.)
Preparing to unpack .../systemd-resolved_255.4-1ubuntu8.1_amd64.deb ...
Unpacking systemd-resolved (255.4-1ubuntu8.1) over (255.4-1ubuntu8.1) ...
Setting up systemd-resolved (255.4-1ubuntu8.1) ...
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
Processing triggers for dbus (1.14.10-4ubuntu4) ...
Processing triggers for man-db (2.12.0-4build2) ...
Config is in use.
Scanning processes...                                                                                                                             
Scanning candidates...                                                                                                                            
Scanning processor microcode...                                                                                                                   
Scanning linux images...                                                                                                                          

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

Restarting services...
 systemctl restart systemd-resolved.service
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.

No containers need to be restarted.

User sessions running outdated binaries:
 aio @ user manager service: chrome[174774,174791,174792,174794,891445,891462,891463,891465], gnome-session-b[169989], gnome-shell[170020],
  surfshark[170400,170719,170720,170767], systemd[169581]

No VM guests are running outdated hypervisor (qemu) binaries on this host.
aio at aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.
aio at aio:~$ service systemd-resolved start
Failed to start systemd-resolved.service: Unit var-tmp.mount is masked.
aio at aio:~$ ls -l /etc/systemd/system/systemd-resolved.service
ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file or directory
aio at aio:~$ sudo ls -l /etc/systemd/system/systemd-resolved.service
ls: cannot access '/etc/systemd/system/systemd-resolved.service': No such file or directory
aio at aio:~$ sudo systemctl daemon-reload
aio at aio:~$ sudo systemctl start systemd-resolved
Failed to start systemd-resolved.service: Unit var-tmp.mount is masked.
aio at aio:~$ sudo systemctl enable systemd-resolved
aio at aio:~$ sudo systemctl start systemd-resolved
Failed to start systemd-resolved.service: Unit var-tmp.mount is masked.
aio at aio:~$ sudo dpkg-reconfigure resolvconf
dpkg-query: package 'resolvconf' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolvconf is not installed
aio at aio:~$ sudo dpkg-reconfigure resolved
dpkg-query: package 'resolved' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolved is not installed
aio at aio:~$ sudo dpkg-reconfigure resolve
dpkg-query: package 'resolve' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.
/usr/sbin/dpkg-reconfigure: resolve is not installed
aio at aio:~$ ping aio
PING aio (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.061 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.040 ms
^C
--- aio ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1030ms
rtt min/avg/max/mdev = 0.040/0.050/0.061/0.010 ms
aio at aio:~$ ping laptop2
ping: laptop2: Name or service not known
aio at aio:~$ sudo systemctl unmask systemd-networkd.service
aio at aio:~$ service systemd-resolved restart
Failed to restart systemd-resolved.service: Unit var-tmp.mount is masked.

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=<set>
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI     WWAN-HW  WWAN
   running  1.45.90  connected  started  full          enabled     enabled  enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions