IIRC, since Ubuntu uses debconf to manage host keys sshd is free to start 
without them and wait for something like cloud-init generate them at its 
leisure.  On Fedora, though, sshd-keygen.service generates them.  Since that 
always runs immediately prior to sshd.service it is much more difficult to make 
sshd start without host keys.  If cloud-init.service does not finish before 
sshd-keygen.service starts then sshd will need a restart to pick up whatever 
changes cloud-init happens to make to it.

Strictly speaking, this patch is incorrect -- cloud-init.service should precede 
sshd.service *and* sshd-keygen.service.
-- 
https://code.launchpad.net/~jordane/cloud-init/sshd-systemd-fix/+merge/224353
Your team cloud init development team is requested to review the proposed merge 
of lp:~jordane/cloud-init/sshd-systemd-fix into lp:cloud-init.

_______________________________________________
Mailing list: https://launchpad.net/~cloud-init-dev
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~cloud-init-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to