pre-seeding lxd on Core appliances breaks console-conf user creation
Bug #1881588 reported by
Oliver Grawert
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Invalid
|
Undecided
|
Ian Johnson | ||
subiquity |
Fix Released
|
Undecided
|
Michael Hudson-Doyle | ||
Core16 |
Won't Fix
|
Undecided
|
Unassigned | ||
Core18 |
Fix Released
|
Undecided
|
Unassigned | ||
Core20 |
Fix Released
|
Undecided
|
Unassigned |
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 ...
description: | updated |
summary: |
- pre-seeding lxd on Core appliances breaks snap create-user + pre-seeding lxd on Core appliances breaks snap console-conf user + creation |
summary: |
- pre-seeding lxd on Core appliances breaks snap console-conf user - creation + pre-seeding lxd on Core appliances breaks console-conf user creation |
affects: | subiquity → subiquity (Ubuntu) |
Changed in snapd: | |
status: | Invalid → New |
Changed in subiquity: | |
status: | New → Incomplete |
Changed in subiquity (Ubuntu): | |
status: | New → Invalid |
Changed in snapd: | |
status: | New → Triaged |
Changed in subiquity (Ubuntu Xenial): | |
status: | Incomplete → Confirmed |
Changed in subiquity (Ubuntu Bionic): | |
status: | Incomplete → Confirmed |
Changed in subiquity: | |
status: | New → Confirmed |
tags: | added: id-5ef638e8ed708765e909cfe8 |
Changed in subiquity: | |
status: | Confirmed → In Progress |
assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
To post a comment you must log in.
Reproduced with uc20 + console-conf from core20 snap. Adding a subiquity bug since there are some bugs with subiquity here. Namely, `snap create-user` actually works fine in this state, I added `dangerous systemd. debug-shell= 1` to the kernel commandline for the uc20 VM, and got a root shell and manually ran `snap create-user` and it worked fine.
I think the main bug here is that console-conf is incorrectly detecting that a user was created previously. However, some additional bugs I see from this situation which may or may not be worth investigating or fixing since they only really arise because console-conf incorrectly thinks there is a user:
* after getting to the "This device is registered to ..." page, the email address is blank, i.e. it verbatim says "This device is registered to ."
* hitting enter on the "This device is registered" page brings you back to the start of console-conf where it says "Press enter to configure"
Also I double checked and when the lxd user is added via seeding like this, before manually creating my own user, `snap managed` returns false, while after creating a user normally through `snap create-user`, `snap managed` returns true, so perhaps that's the check that console-conf should do to see if it should prompt the user to create a user account on the system.