[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
Oliver Grawert
1881588 at bugs.launchpad.net
Fri Jul 3 08:29:31 UTC 2020
while ignoring UID's below 1000 might help in the short term, the
"managed" state has a lot more meanings in brand stores and we will
likely encounter more breakage introduced by it when customers pre-seed
lxd on branded device images so this side of things needs to still be
examined. the lxd user should never turn the device to managed state.
i cant see any code in the lxd snap that would create it, where exactly
does the user creation even happen ?
--
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
More information about the foundations-bugs
mailing list