[Bug 1891952] Please test proposed package

[Brian Murray]

Hello Brian, or anyone else affected,

Accepted friendly-recovery into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/friendly-
recovery/0.2.38ubuntu1.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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:
  Fix Committed
Status in friendly-recovery source package in Focal:
  In Progress
Status in friendly-recovery source package in Groovy:
  Fix Committed

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