[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
Do we need this in the core snap too, or just core18 images? I.e. are all appliance images core18+snapd based? ** Changed in: subiquity (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: subiquity Status: In Progress => Fix Released ** No longer affects: subiquity (Ubuntu Bionic) ** No longer affects: subiquity (Ubuntu Xenial) ** No longer affects: subiquity (Ubuntu) ** Also affects: subiquity/core18 Importance: Undecided Status: New ** Also affects: subiquity/core16 Importance: Undecided Status: New ** Also affects: subiquity/core20 Importance: Undecided Status: New ** Changed in: subiquity/core20 Status: New => Fix Committed ** Changed in: subiquity/core18 Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
I verified that mwhudson's PR is sufficient for UC20 at least, provided it is changed slightly to account for the actual JSON structure. I built a core20 snap with the new python dependencies that console-conf has, and updated the things that the PR changes in the core20 snap and built a snap with the lxd, core18, snapd, pc, core20, and pc-kernel snaps seeded and I was able to use console-conf to create a user. I also verified that the lxd snap had created the lxd user entry in extrausers passwd before running console-conf and it created lxd first, verifying the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
To be clear from my first comment, when seeding the lxd snap, `snap managed` is false, at least on UC20 and UC18. I did not have a chance to test UC16, but it should not be managed on UC16 either... If it is that is indeed a snapd bug, but absent evidence of that I don't think that there is a snapd bug here -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
ok, answering myself again: https://github.com/lxc/lxd-pkg-snap/blob/latest- edge/snapcraft/commands/daemon.start#L192 which simply calls: chroot /var/lib/snapd/hostfs/ \ useradd --system -M -N --home /var/snap/lxd/common/lxd \ --shell /bin/false --extrausers lxd || true i dont see how the system can end up managed here ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
https://paste.ubuntu.com/p/Y9gY9x9w3y/ for more correct indent :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
Yeah, the new logic should work fine.
An alternative for the older logic would be to skip uid < 1000 so we
ignore system users.
Applying something like this worked here:
--- /usr/share/subiquity/console_conf/controllers/identity.py 2018-08-07
15:07:53.0 +
+++ identity.py 2020-07-03 03:12:47.405925882 +
@@ -58,9 +58,13 @@ def get_device_owner():
except FileNotFoundError:
return None
with extrausers_fp:
-passwd_line = extrausers_fp.readline()
-if passwd_line and len(passwd_line) > 0:
-passwd = passwd_line.split(':')
+for line in extrausers_fp:
+line = line.strip()
+if not line:
+continue
+passwd = line.split(':')
+if int(passwd[2]) < 1000:
+continue
result = {
'realname': passwd[4].split(',')[0],
'username': passwd[0],
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881588
Title:
pre-seeding lxd on Core appliances breaks console-conf user creation
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
So I was confused here, I thought that console-conf wasn't running but it is running but not letting you configure an owner. My branch should still help with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
cat /var/lib/snapd/state.json | jq .data.auth.users ^ this would be interesting to see as my understanding is that this being "null" means managed is false whereas if it shows something, then managed is true ** Changed in: snapd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
Let's re-open the snapd side of this then. ** Changed in: snapd Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
answering my own question: ogra@localhost:~$ grep managed /usr/share/subiquity/console-conf-wrapper if [ "$(snap managed)" = "true" ]; then ogra@localhost:~$ grep PRETTY /etc/os-release PRETTY_NAME="Ubuntu Core 18" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
i was thinking the same when i looked at your patch (and noticed the move-around of the "snap managed" code)... are we sure that version of the code is actually in core18 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
There's something I don't understand about this bug though: it must be that having the lxd snap seeded causes "snap managed" to be "true". That seems wrong? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
I think https://github.com/CanonicalLtd/subiquity/pull/794 implements the logic described in comment #6 but I've entirely forgotten how to test this code! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Changed in: subiquity Status: Confirmed => In Progress ** Changed in: subiquity Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
sadly this isnt true anymore (not that the slow boards got faster but we rather started to ignore that fact), all images nowadays run cloud-init by default so python is kind of mandatory and gets executed anyway ... with the focus on raspberry pi the actual embedded hardware is rather ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
IIRC one of the reasons console-conf-wrapper is implemented in shell is because some of our target platforms were too slow / memory constrained to run python as part of the boot process? Is that still true? Because this is starting to get a little complicated for shell now... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Tags added: id-5ef638e8ed708765e909cfe8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
This getting fixed in core18 (at least) is a blocker for 3 Ubuntu Core appliances we're currently preparing so it'd be great if we could get a fix rolled out soon! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Changed in: subiquity (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: subiquity (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: subiquity Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
I have discussed this and upon closer inspection, we actually we do have an API for console-conf to get the username of a managed device, but the logic that console-conf should follow is a bit more convoluted because eventually we may have devices that are managed (and thus should not allow configuring through console-conf), but do not have any users. So console-conf should not assume that a managed has users and that a device that has users is managed. The flow that console-conf should follow is this: if $(snap managed) is true: if $(snap /v2/users) is not nil: for user in $(snap /v2/users): if /home/$user/ exists: display "ssh user@IP..." forever # else fallback to saying there are not managed users display "device managed without user @ IP" else: display console-conf setup screen The first API request for determining if a device is managed can be done with an HTTP GET request to the snapd /v2/system-info endpoint after a device is seeded, looking at the result.managed key. This is the equivalent of running on the command line `snap managed`. The second API request for determining the username of managing users can be done with an HTTP GET request to the snapd /v2/users endpoint, looking at the result key which is a list of user objects. console-conf should iterate over all of these users, starting with the user with the lowest ID (note that the ID here is not a UID, it is an internal tracking mechanism for snapd, essentially first-come first serve for created users), checking if the user has a /home directory, and if the user has a home directory then we presume that the user could login via SSH. The username key is the name of the user that should be displayed in "ssh @IP". @xnox does that all make sense? ** Changed in: snapd Status: Triaged => Invalid ** Changed in: subiquity Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Changed in: snapd Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
Assigning the snapd task to me, I need to chat with Samuele about how console-conf can use the snapd REST API to get the username of a created user (if there is one). ** Changed in: snapd Assignee: (unassigned) => Ian Johnson (anonymouse67) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
waiting on more advice how console-conf (should or should not) query managed state, available users, and if those users can ssh in. ** Changed in: subiquity (Ubuntu Xenial) Status: New => Incomplete ** Changed in: subiquity (Ubuntu Bionic) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
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@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@pi4:~# ./is-managed.sh
System is managed: true
By user: o...@ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881588
Title:
pre-seeding lxd on Core appliances breaks console-conf user creation
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Changed in: snapd Status: Invalid => New ** Changed in: subiquity Status: New => Incomplete ** Changed in: subiquity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
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@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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Also affects: subiquity Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Project changed: subiquity => subiquity (Ubuntu) ** Also affects: subiquity (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: subiquity (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
