New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user

Issue metadata

Status: Verified
Closed: Nov 17
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug

Sign in to add a comment

ImportError: No module named lockfile

Project Member Reported by, Nov 16 Back to list

Issue description

  Traceback (most recent call last):
    File "/usr/local/autotest/server/", line 921, in group_func
      test.runtest(self, url, tag, args, dargs)
    File "/usr/local/autotest/server/", line 302, in runtest
    File "/usr/local/autotest/client/common_lib/", line 894, in runtest
      exec ('import %s' % modulename, local_namespace, global_namespace)
    File "<string>", line 1, in <module>
    File "/usr/local/autotest/server/site_tests/cheets_CTS_N/", line 19, in <module>
      from autotest_lib.server.cros import tradefed_test
    File "/usr/local/autotest/server/cros/", line 25, in <module>
      import lockfile
  ImportError: No module named lockfile

dshi@, how is the package controlled in the lab? any thoughts why lockfile is missing?
That test should run in server-side packaging. Better check if has some ssp issue.

Comment 3 Deleted

Comment 4 Deleted

Status: Assigned

Comment 7 Deleted

Owner: ----
Status: Untriaged
Labels: -Pri-1 Pri-0
ayatane@ just merged the puppet fix
A typo during Puppet refactoring caused enable_ssp_containers to be disabled.  Landed fix and ran puppet.
Status: Fixed
Status: Available
Still seeing the missing lockfile package. Puppet fix isn't enough?
autoserv command is kicked off by scheduler, so the scheduler must be restarted to pick up the change in shadow config. I will make the restart.
Status: Fixed
Status: Verified
Verified. Thanks for your work.

Sign in to add a comment