wlan setup done by console-conf not persistent

[Oliver Grawert]

running console-conf on a dragonboard now configures the wlan0 device just fine, the device is reachable (after looking up the IP on the dhcp server, but this is another bug) by ssh and usable for the created user.

however, after first reboot the network device does not come up anymore and the device is unreachable.

[Michael Hudson-Doyle (mwhudson)]

Argh, I know what's going on here. The snap firstboot job is running on every boot, not just the first, and stomping on the netplan config that console-conf is writing.

[Michael Hudson-Doyle (mwhudson)]

Hm, snapd.firstboot is failing for me like this:

Sep 13 21:17:45 localhost.localdomain systemd[1]: Starting Run snappy firstboot setup...
Sep 13 21:17:48 localhost.localdomain snap[1104]: error: need a model assertion
Sep 13 21:17:48 localhost.localdomain systemd[1]: snapd.firstboot.service: Main process exited, code=exited, status=1/FAILURE
Sep 13 21:17:48 localhost.localdomain systemd[1]: Failed to start Run snappy firstboot setup.
Sep 13 21:17:48 localhost.localdomain systemd[1]: snapd.firstboot.service: Unit entered failed state.
Sep 13 21:17:48 localhost.localdomain systemd[1]: snapd.firstboot.service: Failed with result 'exit-code'.

which suggests that maybe it would work for a fully official signed image? But anyway, this is still bad.

[Oliver Grawert (ogra)]

it seems to work after i fixed bug 1623125 ...
so yes, th3e full signature seems to have some effect here ... closing as invalid