[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation

[Michael Hudson-Doyle]

Yeah, so I think there's two bugs here:

1) having the lxd snap around should not make `snap managed` be true
(this is a bug in snapd I think, although xnox said this might have been
fixed?)

2) console-conf should never suggest that the user logs in as lxd@

My branch fixes 2). If 1) unexpectedly turns out not to be a bug, we can
cope with that in console-conf too, but I'd rather hear from someone on
the snapd team first about that.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1881588

Title:
  pre-seeding lxd on Core appliances breaks console-conf user creation

Status in snapd:
  Invalid
Status in subiquity:
  In Progress
Status in subiquity package in Ubuntu:
  Invalid
Status in subiquity source package in Xenial:
  Confirmed
Status in subiquity source package in Bionic:
  Confirmed

Bug description:
  when seeding appliance images with lxd, user creation gets impossible.

  console-conf skips the user creation, system-user assertions do not
  work either because there is already a user exisiting in the image.

  the tty screen shows instructions to log in with "lxd@<IP ADDRESS>"
  ...

  since the lxd user is a special case hack in Ubuntu Core images, "snap
  create-user ..." should probably learn to ignore its existence ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions