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

[Oliver Grawert]

i dont think there is a snap command to get the managed state (there is
"snap known system-user" but that seems to only work if the user was
actually created with an assertion)

if you actually want shell instead of a simple python http query:

root at pi4:~# cat is-managed.sh 
#! /bin/sh

query_snapd() {
  RET="$(/bin/echo -e 'GET /v2/'"$1"' HTTP/1.0\r\n\r\n' | \
           nc -U /var/run/snapd.socket -q0 2>&1 | \
           grep -oP '(^.*"'"$2"'":)[^,]*' | \
           grep -o '[^:]*$')"
  echo "$RET" | sed 's/\]//g;s/\}//g;s/\"//g'
}

echo "System is managed: $(query_snapd system-info managed)"
echo "By user: $(query_snapd users email)"
root at pi4:~# ./is-managed.sh 
System is managed: true
By user: ogra at ubuntu.com

-- 
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:
  New
Status in subiquity:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid
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