[Bug 1891952] Re: systemd-resolved not started when networking enabled

[Launchpad Bug Tracker]

This bug was fixed in the package friendly-recovery - 0.2.42

---------------
friendly-recovery (0.2.42) unstable; urgency=medium

  [ Debian Janitor ]
  * Trim trailing whitespace.
  * Add missing build dependency on dh addon.
  * Bump debhelper from old 10 to 12.
  * Set debhelper-compat version in Build-Depends.
  * Use secure URI in Vcs control header Vcs-Bzr.

  [ William 'jawn-smith' Wilson ]
  * add resolvconf-pull-resolved.path to script that brings up the
    network (LP: #1891952)

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Wed, 27 Jan 2021 15:54:45
+0000

** Changed in: friendly-recovery (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1891952

Title:
  systemd-resolved not started when networking enabled

Status in Release Notes for Ubuntu:
  Fix Released
Status in friendly-recovery package in Ubuntu:
  Fix Released
Status in friendly-recovery source package in Bionic:
  New
Status in friendly-recovery source package in Focal:
  New
Status in friendly-recovery source package in Groovy:
  New

Bug description:
  I was using friendly-recovery as my Ubuntu desktop session was not
  starting after an upgrade to Groovy Gorilla. When I chose to "Enable
  networking" in the friendly-recovery menu I noticed that no dns
  servers could be reached and come to find out it was because systemd-
  resolved did not start.

  Attached is a photo with some additional information.

  [Impact]

   * If a user has both systemd and resolvconf
     installed, the networking option in friendly
     recovery mode will not work correctly.

   * In this scenario, /etc/resolv.conf will be
     empty and dns resolution will not work

  [Test Case]

   * Ensure both systemd and resolvconf are installed

   * Boot to friendly recovery mode and select the
     network option from the menu

   * Drop to a root shell by selecting the root shell
     option from the menu.

   * `cat /etc/resolv.conf` to make sure it is not
      an empty file

   * Run `dig www.google.com` to ensure dns resolution
     works properly

  [Where problems could occur]

   * It is possible certain resolvconf or systemd-resolved
     configurations could still conflict with each other

   * This would be especially true if a user wanted to use
     one nameserver service for a fully booted system and
     a different service in friendly recovery mode

   * If the nameserver is misconfigured in resolvconf or
     network-manager, it will still be non-functional
     in friendly recovery mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1891952/+subscriptions