If the loopback interface is managed via Netplan with network-manager, netplan apply will take it down and NM will not bring it back
Bug #2034595 reported by
Danilo Egea Gondolfo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| netplan.io (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
NM is not bringing the loopback interface back automatically after netplan apply flushes its addresses. It's not clear if it's a bug in NM or intended behavior.
It's bad because we have services listening on the loopback interface, such as resolved.
How to reproduce:
1) Install network-manager in Mantic and let it manage at least one of your interfaces. You'll see it's managing 'lo' automatically
2) Try to change the 'lo' connection, something like nmcli con mod lo mtu 1500 NM will emit a YAML (an nm-device) for 'lo'
3)Run netplan apply
4)You'll see that the 'lo' connection is down and the 'lo' interface has no IPs
You can bring it back with nmcli con up lo
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in netplan.io (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package netplan.io - 0.107-5
---------------
netplan.io (0.107-5) unstable; urgency=medium
* d/p/lp2034595: Fix NetworkManager loopback interaction (LP: #2034595)
-- Lukas Märdian <email address hidden> Thu, 14 Sep 2023 17:08:13 +0530