[network-manager] Explicitly configuring an eth interface with netplan makes ipv4.method=manual

Bug #1771842 reported by Alfonso Sanchez-Beato
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snappy-hwe-snaps
Incomplete
Undecided
Unassigned

Bug Description

If we have these two files in /etc/netplan:

$ cat /etc/netplan/00-default-nm-renderer.yaml
network:
  renderer: NetworkManager

$ cat /etc/netplan/00-snapd-config.yaml
network:
  version: 2
  ethernets:
    eth0:
      dhcp4: true

Then

$ nmcli connection show eth0
...
ipv4.method: manual
...

It turns out that the "dhcp4: true" line is not respected and we end up in a system where the eth0 connection has method "manual" for setting the IP address. We end up with a badly configured system where we be without DNS addresses in /etc/resolv.conf, for instance.

Other strange things happens, for instance:

$ nmcli c modify eth0 ipv4.method auto

creates a new connection with the same name (eth0), instead of modifying the previous one.

Revision history for this message
Tony Espy (awe) wrote :

This bug list is meant to track issues with snaps maintained in this project (meant for usage on Ubuntu Core only). If you have issues with bluetooth on Ubuntu Desktop, please use the Ubuntu network-manager bug list: https://bugs.launchpad.net/ubuntu/+source/network-manager.

If this bug does involve the network-manager snap on Ubuntu Core, then please provide additional details:

- the output of `snap list`
- the version of Ubuntu Core
- more details on your use case, steps to reproduce

Changed in snappy-hwe-snaps:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.