Red Hat Bugzilla – Bug 1288657
could not lock client after bailing on suspend
Last modified: 2017-04-22 22:30:51 EDT
Description of problem:
When running the suspend test, attempting to exit the suspend test causes the interface to fail with "could not lock client" as the status. This stays as the status after the next test runs, and even after the daemon is restarted and the web page reloaded.
Version-Release number of selected component (if applicable):
error occurs consistently when lock file is created and a test crashes.
Steps to Reproduce:
1. run an interactive test on a laptop (lid, in the example)
2. attempt to bail out of the mandatory suspend test by selecting "no" for its prompts and clicking the "back" link to go to the test results page.
3. continue through suspend test (it won't restart, even when the link is clicked)
4. continue through the interactive (lid) test. This will fail.
5. after test completion and return to results page, attempt to launch another test.
The error message is printed as status, and on the interactive test screen:
Error: could not lock client
There is no way to proceed to tests.
removing the lock file and restarting the daemon have no effect.
Test fails gracefully (no stops or hangs) without lock file error, allowing testing to continue.
Looking for smaller set of conditions required to trigger.
I'm still unsure whether this is a generic problem in redhat-certification, or a problem specific to suspend or -hardware tests.
restarting the daemon again causes the system to return to the expected state. So it's possible that's a workaround, still investigating if that's the common case.
Also, I clicked "restart" during the suspend test's execution, which triggers bz 1277191
How did you "exit" the suspend test? By pressing "No", or some other means?