| 2022-07-08 18:47:29 |
Uwe Schindler |
bug |
|
|
added bug |
| 2022-08-18 00:23:00 |
Launchpad Janitor |
ifupdown (Ubuntu): status |
New |
Confirmed |
|
| 2022-08-18 00:23:33 |
Chris Nicolson |
bug |
|
|
added subscriber Chris Nicolson |
| 2022-10-12 09:17:53 |
Lukas Märdian |
tags |
|
foundations-triage-discuss |
|
| 2022-10-12 09:18:00 |
Lukas Märdian |
ifupdown (Ubuntu): status |
Confirmed |
Triaged |
|
| 2022-10-12 09:18:03 |
Lukas Märdian |
ifupdown (Ubuntu): importance |
Undecided |
Medium |
|
| 2022-11-10 16:30:04 |
Lukas Märdian |
bug |
|
|
added subscriber Lukas Märdian |
| 2022-11-10 16:33:28 |
Lukas Märdian |
tags |
foundations-triage-discuss |
|
|
| 2023-08-23 18:09:43 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu): assignee |
|
Heitor Alves de Siqueira (halves) |
|
| 2023-08-23 18:09:46 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu): status |
Triaged |
In Progress |
|
| 2023-09-06 18:19:49 |
Heitor Alves de Siqueira |
bug |
|
|
added subscriber Heitor Alves de Siqueira |
| 2023-09-06 18:49:58 |
Heitor Alves de Siqueira |
attachment added |
|
lp1981103.debdiff https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+attachment/5698057/+files/lp1981103.debdiff |
|
| 2023-09-06 18:50:38 |
Heitor Alves de Siqueira |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-09-07 13:35:54 |
Benjamin Drung |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-09-07 13:38:37 |
Benjamin Drung |
ifupdown (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2023-09-07 13:38:42 |
Benjamin Drung |
bug |
|
|
added subscriber Benjamin Drung |
| 2023-09-07 23:55:04 |
Launchpad Janitor |
ifupdown (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2023-10-11 18:12:38 |
Heitor Alves de Siqueira |
description |
Description: Ubuntu 22.04 LTS
Release: 22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using /etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors, easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious bug and should be fixed before 22.04 upgrades are allowed for everybody. Most servers provided by data centers like Hetzner (Germany) are configure like that. After a do-release-upgrade you have no working DNS anymore, unless you disable systemd-resolved. I don't want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side "$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <<EOF >"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <<EOF >>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi |
[ Impact ]
ifupdown configurations will stop having a working DNS server on upgrade
[ Test Plan ]
Upgrading from an Ubuntu 18.04 or earlier release, bounce a network interface with configured DNS server:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This should result in no errors, and in a valid network configuration with working DNS resolution.
It's likely that existing netplan configuration needs to be removed and migrated to classic ifupdown scripts before running the test above.
[ Where problems could occur ]
Although we're only fixing the resolved scripts, more complex network setups might see regressions in DNS resolution for some cases. We should pay special attention to bridges or virtual interfaces that have been configured through ifupdown, as well as validate the other scripts under /etc/network/if-up.d/
[ Other Info ]
Description: Ubuntu 22.04 LTS
Release: 22.04
ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
*** 0.8.36+nmu1ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status
After upgrading a server with classic ifupdown configuration after reboot the machine had no valid dns servers anymore.
The problem is that the state file created by ifupdown using /etc/network/if-up.d/resolved looks like this:
root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
"DNS"="134.102.20.20 134.102.200.14"
"DOMAINS"="marum.de"
The script later sources this file and causes the following errors, easy to see when you execute this:
root@pangaea-pm:~# ifdown ens13; ifup ens13
/etc/network/if-down.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 12: mystatedir: not found
/etc/network/if-up.d/resolved: 71: DNS: not found
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: DNS=134.102.20.20 134.102.200.14: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: DOMAINS=marum.de: not found
Failed to parse DNS server address: DNS
Failed to set DNS configuration: Invalid argument
This happened to me on three different servers, so this is a serious bug and should be fixed before 22.04 upgrades are allowed for everybody. Most servers provided by data centers like Hetzner (Germany) are configure like that. After a do-release-upgrade you have no working DNS anymore, unless you disable systemd-resolved. I don't want to use netplan, so changing to this is no option.
The fix is easy - remove the quotes in the script on the left side "$DNS" => $DNS; same for DOMAINS:
if [ -n "$NEW_DNS" ]; then
cat <<EOF >"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DNS="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <<EOF >>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
$DOMAINS="$NEW_DOMAINS"
EOF
fi
fi |
|
| 2023-10-11 18:13:16 |
Heitor Alves de Siqueira |
nominated for series |
|
Ubuntu Focal |
|
| 2023-10-11 18:13:16 |
Heitor Alves de Siqueira |
bug task added |
|
ifupdown (Ubuntu Focal) |
|
| 2023-10-11 18:13:16 |
Heitor Alves de Siqueira |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-10-11 18:13:16 |
Heitor Alves de Siqueira |
bug task added |
|
ifupdown (Ubuntu Jammy) |
|
| 2023-10-11 18:13:16 |
Heitor Alves de Siqueira |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-10-11 18:13:16 |
Heitor Alves de Siqueira |
bug task added |
|
ifupdown (Ubuntu Lunar) |
|
| 2023-10-11 18:13:23 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Focal): assignee |
|
Heitor Alves de Siqueira (halves) |
|
| 2023-10-11 18:13:25 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Jammy): assignee |
|
Heitor Alves de Siqueira (halves) |
|
| 2023-10-11 18:13:26 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Lunar): assignee |
|
Heitor Alves de Siqueira (halves) |
|
| 2023-10-11 18:13:27 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Focal): status |
New |
In Progress |
|
| 2023-10-11 18:13:29 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Jammy): status |
New |
In Progress |
|
| 2023-10-11 18:13:31 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Lunar): status |
New |
In Progress |
|
| 2023-10-11 18:13:33 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Focal): importance |
Undecided |
Low |
|
| 2023-10-11 18:13:35 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Lunar): importance |
Undecided |
Critical |
|
| 2023-10-11 18:13:36 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Jammy): importance |
Undecided |
Low |
|
| 2023-10-11 18:13:38 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Lunar): importance |
Critical |
Low |
|
| 2023-10-17 13:29:54 |
Heitor Alves de Siqueira |
ifupdown (Ubuntu Focal): status |
In Progress |
Fix Released |
|
