Chrome Version: M62-9886.0.0
OS: ChromeOS

What steps will reproduce the problem?
(1) install new DUT for moblab
(2) Install appropriate EC, BIOS, and ChromeOS image into DUT
(3) Setup DUT within moblab
(4) Run FAFT in Moblab

What is the expected result?
Test should start running and tests should pass.

What happens instead?

All test fails fairly quick.

In my discussion with Keith Haddow, he believes that this CL broke this.

https://chromium-review.googlesource.com/#/c/chromiumos/third_party/autotest/+/564140/

Please use labels and text to provide additional information.

One of the output from the log are:
FAIL	----	----	timestamp=1503955997	localtime=Aug 28 14:33:17	Failed to run test inside the container: Command <sudo lxc-attach -P /mnt/moblab/containers -n test_2_1503955978_12612 -- bash -c "/usr/local/autotest/server/autoserv -p -r /usr/local/autotest/results/2-moblab -m 192.168.231.100 -u moblab -l caroline-release/R62-9886.0.0/faft_ec/firmware_RONormalBoot.ec_wp -s --lab True -P /usr/local/autotest/results/2-moblab -n /usr/local/autotest/drone_tmp/attach.4 --verify_job_repo_url --use-existing-results --pidfile-label container_autoserv"> failed, rc=1, Command returned non-zero exit status
  * Command: 
      sudo lxc-attach -P /mnt/moblab/containers -n test_2_1503955978_12612 --
      bash -c "/usr/local/autotest/server/autoserv -p -r
      /usr/local/autotest/results/2-moblab -m 192.168.231.100 -u moblab -l
      caroline-release/R62-9886.0.0/faft_ec/firmware_RONormalBoot.ec_wp -s --lab
      True -P /usr/local/autotest/results/2-moblab -n
      /usr/local/autotest/drone_tmp/attach.4 --verify_job_repo_url --use-
      existing-results --pidfile-label container_autoserv"
  Exit status: 1
  Duration: 0.62344789505
  
  stderr:
  Traceback (most recent call last):
    File "/usr/local/autotest/server/autoserv", line 35, in <module>
      metrics = utils.metrics_mock
  NameError: name 'utils' is not defined. Check logs in ssp_logs folder for more details.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.