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 protected] 2) Adding a system-user assertion snappy: assertions: - | <system user assertion> email: [email protected] 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. ** Changed in: cloud-init Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1683542 Title: After configuing Ubuntu Core system still displays subiquity wizard Status in cloud-init: Won't Fix Bug description: After deploying Ubuntu-Core using MAAS the console-conf 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 console-conf should be disabled as cloud-init has already created a user. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1683542/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
