[bionic] Installing desktop from mini.iso results in ambiguous configuration

[Mike Pontillo]

Not sure where to put this bug, but I'll start here (apologies). I'm not actually sure if it's a bug or intended behavior, but if it's intended, it would be nice if the files the installer places down include better comments (or simply delete the no-longer-relevant file).

I installed Bionic using mini.iso and selected Ubuntu Desktop.

It seems that two Netplan configurations are generated; it's not clear if this is correct, and it's not clear which configuration takes precedence. It looks like NetworkManager eventually took control of the interface, as seen below:

mpontillo@bionic:/etc/netplan$ ls -l
total 8
-rw-r--r-- 1 root root 194 Nov 10 19:25 01-netcfg.yaml
-rw-r--r-- 1 root root 104 Nov 10 19:36 01-network-manager-all.yaml

mpontillo@bionic:/etc/netplan$ cat *
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
    ens33:
      dhcp4: yes
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager

mpontillo@bionic:~$ nmcli
ens33: connected to netplan-ens33
 "Intel 82545EM Gigabit Ethernet Controller (Copper) (PRO/1000 MT Single Port Adapter)"
 ethernet (e1000), 00:0C:29:90:B1:90, hw, mtu 1500
 ip4 default
 inet4 172.16.230.129/24
 route4 169.254.0.0/16
 inet6 fe80::20c:29ff:fe90:b190/64

lo: unmanaged
 "lo"
 loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
 servers: 172.16.230.2
 domains: localdomain
 interface: ens33

...

mpontillo@bionic:~$ networkctl
WARNING: systemd-networkd is not running, output will be incomplete.

IDX LINK TYPE OPERATIONAL SETUP
  1 lo loopback n/a unmanaged
  2 ens33 ether n/a unmanaged

2 links listed.

[Mathieu Trudel-Lapierre (cyphermox)]

Nice catch. This is a bug in netcfg, reassigning.