After configuing Ubuntu Core system still displays subiquity wizard

This just a matter of 'touch /var/lib/console-conf/complete' or equivalent.

On 18 April 2017 at 11:57, Lee Trager <email address hidden> wrote:

> Public bug reported:
>
> After deploying Ubuntu-Core using MAAS the subiquity wizard still runs
> on the deployed system. With it a person with physical/console access
> can change networking configuration and add a user which has sudo
> access. When cloud-init runs and creates a user subiquity should be
> disabled as cloud-init has already created a user.
>
> ** Affects: cloud-init
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Canonical
> Cloudware, which is subscribed to cloud-init.
> Matching subscriptions: cloud-init bugs
> https://bugs.launchpad.net/bugs/1683542
>
> Title:
> After configuing Ubuntu Core system still displays subiquity wizard
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1683542/+subscriptions
>

On Mon, Apr 17, 2017 at 11:57:30PM -0000, Lee Trager wrote:
> Public bug reported:

> After deploying Ubuntu-Core using MAAS the subiquity wizard still runs
> on the deployed system. With it a person with physical/console access
> can change networking configuration and add a user which has sudo
> access. When cloud-init runs and creates a user subiquity should be
> disabled as cloud-init has already created a user.

I believe this would be dependent on maas driving cloud-init to create the
right /kind/ of user on an ubuntu-core install. There is a different key to
use for linking an ubuntu-core install to a store account, which is the
prerequisite for the console-conf wizard being suppressed.

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.

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/2861