[Bug 1879485] Re: Automated Install does not set default user data

[Michael Hudson-Doyle]

I've committed the fix that sets the lock_passwd key instead of the
lock-passwd key, so if you can test with:

refresh-installer:
    channel: edge
    update: yes

in your config, I would appreciate it.

I still don't understand at all why nocloud vs nocloud-net makes a
difference. It really shouldn't!

** Changed in: subiquity
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1879485

Title:
  Automated Install does not set default user data

Status in subiquity:
  Fix Committed
Status in subiquity package in Ubuntu:
  Confirmed

Bug description:
  When I run the automated installer I always end up with a fresh system
  I cannot login to. The default user ubuntu has its password locked.

  I tested this using the minimalistic example from the [wiki][1],
  latest Focal and virtualbox.

  cat > user-data << 'EOF'
  #cloud-config
  autoinstall:
    version: 1
    identity:
      hostname: ubuntu-server
      password: "$6$exDY1mhS4KUYCE/2$zmn9ToZwTKLhCw.b4/b.ZRTIZM30JZ4QrOQ2aOXJ8yk96xpcCof0kxKwuX1kqLG/ygbJ1f8wxED22bTL4F46P0"
      username: ubuntu
  EOF
  touch meta-data

  cloud-localds ~/seed.iso user-data meta-data

  I tried to get in using these ways, too:

  1. Adding a SSH key to an additional `ssh` section did not help as well.
  2. Configuring a user in user-data did not work as well.

  Actually, no settings from the `user-data` section work but
  configuration from the storage and network sections works like a
  charm.

  [1]:
  https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/QuickStart#Using_another_volume_to_provide_the_autoinstall_config

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1879485/+subscriptions