Sergio[1] got access to the actual container that failed to run this test, and we tried to troubleshoot it a bit. We were pressed for time, and didn't get very far.
What we did/tried: - reproduced the problem at will, in every single test run, interactively - verified that the ldap setup was sound. We changed the expect script to work via ssh <testuser>@localhost, and the test passed - we realised that /usr/bin/login in debian and in ubuntu are different. The debian one comes from util-linux, whereas the ubuntu one comes from shadow - in that session, whenever we tried to run login directly, to manually test a login, that would disconnect us from the session We might try again with more ideas, but here are some: - change the test to use ssh instead of /usr/bin/login. We will never know what was going on, but the test should work - get shell on the container again, and run some more experiments. Perhaps strace with expect, or login, which we forgot, but also the fact we would get dropped whenever running login is suspiscious, and maybe strace wouldn't get a chance to show us what is going on - I didn't spot any funny business around ttys and terminals, other than running login would kick us out We can keep at it, but we also have some options to move forward now (above, and in my previous comment). What does everybody else think? 1. https://wiki.debian.org/SergioDuriganJunior
