Comment 3 for bug 1691826

1. I did not intend to set it up as cloud-init. I assumed it got flagged because I tagged it with systemd-boot. Sorry if that messed things up. I'm not even sure what packages cloud-init covers. If it is not appropriate, it should be deleted.

2. The system this resides on is part of a cluster used for quantum computations. It is usually isolated from the networks. With minimum luck I will have time to transfer over the nss_ldap config and the requested logs today. However, your last question suggests what is probably the issue. I did not intentionally move sshd to ldap, but when this problem occurred I found that that is where it now resides. I am quite suspicious that is the actual problem. The other nodes on my system have a local sshd user. They are still running 14.0.4 rather than 16.04. The node I am having issues with is not used for computations, so gets used for initial upgrade testing.