Comment 5 for bug 1846355

Hi Anisse,

Thanks for using cloud-init, and for taking the time to file a bug! I'm going to mark this as a duplicate of bug 1834190, as the source of the issue is snapd.seeded being unacceptably slow. Apologies for that, we're hoping to see some improvements from that team in the near future.

Unfortunately, I don't think there's currently a great way to work around this problem other than using an SSH key. In the baked-in configuration (which you can see in /etc/cloud/cloud.cfg), `users-groups` is one of the last things to run in the init stage (right before `ssh`, which is what configures the SSH keys). As such, there isn't really any way for you to interject any manual password configuration.

One option would be to modify the image to either (a) modify cloud.cfg to move set-passwords, (b) add your own systemd unit which does the password configuration (and has After=cloud-init-local.service), or (c) disable snapd.seeded. (None of these are options that we'd necessarily be able to provide much support for, I'm afraid.)

Sorry to be the bearer of bad news, hopefully the snapd team will deliver soon!

Thanks again,

Dan