Temporary failure in name resolution on Ubuntu server 22.04.3 LTS

[Bo Berglund]

On Sun, 26 Nov 2023 15:18:42 +0100, Bo Berglund <bo.berglund at gmail.com> wrote:

>2) The references to NetworkManager in most of the web hits I have read
>concerning the resolution to this problem do not work. For instance:
>- nmcli does not exist
>  $ nmcli
>  Command 'nmcli' not found, but can be installed with:
>  sudo snap install network-manager  # version 1.2.2-31, or
>  sudo apt  install network-manager  # version 1.36.6-0ubuntu2
>  See 'snap info network-manager' for additional versions.

So I have now checked if Networkmanager is actually installed on the server
having the networking issues.
This check is done using apt on that server:

$ apt policy network-manager
network-manager:
  Installed: (none)
  Candidate: 1.36.6-0ubuntu2
  Version table:
     1.36.6-0ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
     1.36.4-2ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

It seems like network-manager is *not* installed, so something else is running
the network interfaces (and failing as described in this thread)...
How come this has not been corrected during the do-release-upgrade I have done a
number of times on this server ( 16 -> 18 -> 20 -> 22)

OTOH:
By looking at the response to the nmcli start attempt above it seems like it
wants network-manager to be a snap service....
I think snap is not really part of this old system, but how can I check?


If I want to get to the proper system copnfig with a stable networking system
can I do this simply using:

sudo apt install network-manager
or should it be some snap oriented command (I have never used snap myself)
I had a try at seeng what is here:

$ snap services
Service                                   Startup  Current   Notes
canonical-livepatch.canonical-livepatchd  enabled  active    -
lxd.activate                              enabled  inactive  -
lxd.daemon                                enabled  inactive  socket-activated


And will this require some manual tweakings, which might make services like
OpenVPN server not work after a reboot following the install?
If that happens then I am locked out of the server since OpenVPN is the one
making me able to connect to the remote site...


-- 
Bo Berglund
Developer in Sweden