snapd firstboot setup fails constantly when rebooting before console-conf has finished

[Oliver Grawert]

console-conf currently does not dynamically detect if ethernet cables get plugged in.
if you forget to plug your board in you are not able to configure the network properly ...
rebooting the board will never clear the state of the snapd firstboot job, it runs on every boot and will fail on every boot, leaving you with a broken state and snap list will report no snaps installed.

the only way out of this is to freshly dd the image and start over with the ethernet cable plugged in before boot.

there are two bugs here, snapd's firstboot job should never go into this state and console-conf should auto-detect plug events and dynamically update the UI to allow configuring the interface without forcing a reboot (this is partially bug 1623897)

[Michael Hudson-Doyle (mwhudson)]

I don't understand the stuff about firstboot, sorry.

[Michael Hudson-Doyle (mwhudson)]

I think all the console-conf bits are fixed in the edge core snap now.

[Michael Vogt (mvo)]

The code that does the firstboot got reworked. Instead of having a stamp file and a systemd job its now all internal. This means that the issue that a early reboot sends it into an endless loop is fixed.