Comment 3 for bug 1683542

I'm marking this as wont-fix from a cloud-init perspective. There's likely a maas task on how best to expose this to users.

This is working as designed. As Steve pointed out, while cloud-init may have created other users, they're not 'system-users' which has been authenticated with the Ubuntu Store. Thus on Ubuntu-core, console-conf will run unless the system has a 'system-user' registered. This can be achieved a number of ways.

1) Adding user-data to start the registration process:

snappy:
  email: <email address hidden>

2) Adding a system-user assertion

snappy:
  assertions:
  - |
  <system user assertion>
  email: <email address hidden>
  known: true

3. running console-conf manually

Cloud-init may create other users on the system, but they're not system-users and are not connected to the store and may not initially perform snap commands or have access to certain snaps in the store without registering/logging in.