@jdstrand the issue here is that the connection for the network-manager interface from the network-manager:nmcli plug is not auto-connected to the network-manager:service slot in the network-manager snap on classic.
However, on core, the same interface is auto-connected. This sounds like a bug then, no?
After installing the network-manager snap on classic in a multipass VM:
multipass@organic-kudu:~$ snap connections network-manager
Interface Plug Slot Notes
dbus network-manager:wpa - -
firewall-control network-manager:firewall-control :firewall-control -
modem-manager network-manager:modem-manager :modem-manager -
network network-manager:network :network -
network-manager - network-manager:service -
network-manager network-manager:nmcli - -
network-setup-observe network-manager:network-setup-observe :network-setup-observe -
ppp network-manager:ppp :ppp -
after installing in a UC16 VM:
multipass@revered-goby:~$ snap connections network-manager
Interface Plug Slot Notes
dbus network-manager:wpa - -
firewall-control network-manager:firewall-control :firewall-control -
modem-manager network-manager:modem-manager - -
network network-manager:network :network -
network-manager network-manager:nmcli network-manager:service -
network-setup-observe network-manager:network-setup-observe :network-setup-observe -
ppp network-manager:ppp :ppp -
The assertion in the bionic classic VM:
type: snap-declaration
format: 2
authority-id: canonical
revision: 25
series: 16
snap-id: RmBXKl6HO6YOC2DE4G2q1JzWImC04EUy
aliases:
-
name: nmcli
target: nmcli
auto-aliases:
- nmcli
plugs:
dbus:
allow-auto-connection:
-
plug-attributes:
name: $SLOT(name)
slot-attributes:
name: fi.epitest.hostap.WPASupplicant
-
plug-attributes:
name: $SLOT(name)
slot-attributes:
name: fi.w1.wpa_supplicant1
firewall-control:
allow-auto-connection: true
hardware-observe:
allow-auto-connection: true
modem-manager:
allow-auto-connection: true
network-manager:
allow-auto-connection: true
network-setup-control:
allow-auto-connection: true
network-setup-observe:
allow-auto-connection: true
ppp:
allow-auto-connection: true
publisher-id: canonical
slots:
network-manager:
allow-connection: true
allow-installation:
slot-snap-type:
- app
deny-auto-connection: true
snap-name: network-manager
timestamp: 2019-07-01T21:47:45.571440Z
sign-key-sha3-384: BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
The assertion in UC16 is the same as the one in bionic classic:
type: snap-declaration
format: 2
authority-id: canonical
revision: 25
series: 16
snap-id: RmBXKl6HO6YOC2DE4G2q1JzWImC04EUy
aliases:
-
name: nmcli
target: nmcli
auto-aliases:
- nmcli
plugs:
dbus:
allow-auto-connection:
-
plug-attributes:
name: $SLOT(name)
slot-attributes:
name: fi.epitest.hostap.WPASupplicant
-
plug-attributes:
name: $SLOT(name)
slot-attributes:
name: fi.w1.wpa_supplicant1
firewall-control:
allow-auto-connection: true
hardware-observe:
allow-auto-connection: true
modem-manager:
allow-auto-connection: true
network-manager:
allow-auto-connection: true
network-setup-control:
allow-auto-connection: true
network-setup-observe:
allow-auto-connection: true
ppp:
allow-auto-connection: true
publisher-id: canonical
slots:
network-manager:
allow-connection: true
allow-installation:
slot-snap-type:
- app
deny-auto-connection: true
snap-name: network-manager
timestamp: 2019-07-01T21:47:45.571440Z
sign-key-sha3-384: BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul