Comment 9 for bug 1676977

I also believe that this issue is related to systemd. I filed this issue on libpam-ldap because I don't know exactly which systemd service might be wrong and so don't know exactly what package exactly should be changed.

"When the login service fails, did you obtain the logs for it to see why it failed?"

On the previously attached log the boot starting at Mar 28 14:09:29 is a failed boot, i.e., one where the system halts during boot without ever presenting the login prompt.

I can't identify an exact reason for the failure. But I bet that it's related to the fact that the Login service starts together with the Network service making the Login service start without a functional Network connection as you said.

"Finally, is this reproducible with 17.04?"

I'm installing 17.04 in a test station right now. I will report when I finish the tests on it.

"If you are dropped to an emergency shell on failure to boot, does name resolution period work?"

I never managed to do that. I would like to try it. How could I do it?