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

[Dimitri John Ledkov]

Currently consoleconf is not using snapd apis to determine if the
machine is managed, and what are the user ids managing the system.

Can snapd team please double check which commands / APIs should be used?

I.e. what shall we use to query if the machine is managed (and thus
show/skip console-conf UX), and also what shall we use to query userids
to show how to login (i.e. ssh xnox at ip)?

Is https://github.com/snapcore/snapd/wiki/REST-API#get-v2users and
https://github.com/snapcore/snapd/wiki/REST-API#get-v2system-info the
right things?

I think console-conf also still has shell scripts, are there `snap`
command ways to figure that out?

-- 
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:
  New
Status in subiquity package in Ubuntu:
  New
Status in subiquity source package in Xenial:
  New
Status in subiquity source package in Bionic:
  New

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