Comment 1 for bug 1911680

Hi Kevin,

Thanks for using cloud-init, and for taking the time to file such a detailed bug! Apologies for having broken your workflow.

I can reproduce the issue that you're seeing locally, and I'm going to start digging into what we need to do to address it.

I have one clarifying question: when launching an image with an older cloud-init and sshd_config as described, I don't see /etc/ssh/authorized_keys created or populated. As best I can tell, cloud-init places keys in per-user .ssh/authorized_keys regardless of the AuthorizedKeysFile set in sshd_config. Does this match the behaviour you were seeing previously? (I believe this is the bug that we were setting out to fix in the commits you've linked, so I'm not necessarily surprised by this: I just want to make sure that we're all on the same page as far as expected behaviour goes.)

Thanks!

Dan