Remote test session paused indefinitely when session was disconnected

[Jeff Lane ]

Honestly, I have no idea how to reproduce this. I discovered it while looking into this bug against testflinger:

https://bugs.launchpad.net/testflinger/+bug/1905094

In that bug, note the second disconnect example for Drapion. In that case, testflinger showed that there was a disconnection and then it was never able to reconnect, and eventually the testflinger instance exited.

Now in the course of investigating that, I got the idea to just try connecting manually to the SUT via checkbox remote myself. I had expected to find that the test session had completed silently in the background. What I found instead, was that the test session (which is fully automated, including submission to C3) had paused and only resumed testing after I manually connected to the session from my own desktop.

As the remote sessions are supposed to continue running headless, I'm a bit baffled as to why this one paused execution and waited for me to manually reconnect.

Also note, despite what the error messages in the above bug say, I did NOT, at any time, connect to the checkbox session from anywhere else. I merely fired off testflinger and walked away to wait for them to complete. I only connected to the session a couple days after the fact, expecting to find it already completed.

[Maksim Beliaev (beliaev-maksim)]

Bug was migrated to GitHub: https://github.com/canonical/checkbox/issues/150.
Bug is no more monitored here.