shouldn't that be an ssh bug then?
Was there any reason to flag cloud-init - maybe you used cloud-init to
set that up?
** Also affects: openssh (Ubuntu)
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
systemd script for sshd allows it to start too early should wait for
Status in cloud-init package in Ubuntu:
Status in openssh package in Ubuntu:
After the most recent update to 16.04 I found that sshd failed to
launch on bootup. On my particular system this is because it was not
able to authenticate the user 'sshd'. It appears to be because it is
starting before authentication services are completely available on my
system. A simple fix was to make the following change to
++After=network.target auditd.service accounts-daemon.service
Starting too early might be a security issue, but I do not have the
expertise to make that judgment. This may also be related to and solve
this bug #1024475 as I am also serving some of my accounts from ldap.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp