systemd-resolved not started when networking enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
friendly-recovery (Ubuntu) |
Fix Released
|
High
|
William Wilson | ||
Bionic |
Fix Released
|
High
|
William Wilson | ||
Focal |
Fix Released
|
High
|
William Wilson | ||
Groovy |
Fix Released
|
High
|
William Wilson |
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.
Related branches
- Brian Murray: Needs Information
- Dimitri John Ledkov: Approve (lgtm)
-
Diff: 35 lines (+7/-2)2 files modifieddebian/changelog (+6/-1)
lib/recovery-mode/options/network (+1/-1)
tags: | removed: rls-gg-incoming |
Changed in friendly-recovery (Ubuntu Groovy): | |
importance: | Undecided → High |
tags: | added: id-5f3e933949c90824f3719caa |
tags: | added: fr-209 |
tags: | added: groovy |
Changed in ubuntu-release-notes: | |
status: | New → Fix Released |
description: | updated |
Changed in friendly-recovery (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in friendly-recovery (Ubuntu Focal): | |
importance: | Undecided → High |
Changed in friendly-recovery (Ubuntu): | |
assignee: | nobody → William Wilson (jawn-smith) |
Changed in friendly-recovery (Ubuntu Bionic): | |
assignee: | nobody → William Wilson (jawn-smith) |
Changed in friendly-recovery (Ubuntu Focal): | |
assignee: | nobody → William Wilson (jawn-smith) |
Changed in friendly-recovery (Ubuntu Groovy): | |
assignee: | nobody → William Wilson (jawn-smith) |
The problem I encountered in the description was from when I had systemd version 246-2ubuntu1 installed. I've since downgraded to 245.7-1ubuntu1 so I tried friendly-recovery again and there were still issues with name resolution. However, this time starting systemd-resolved did not fix the issue and name resolution still failed so I think this bears further investigation.