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 2 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Mar 29
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: ----



Sign in to add a comment

No module named pbr.version in container

Project Member Reported by xixuan@chromium.org, Dec 1 2017

Issue description

Failed job in veyron_speedy-paladin:
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/159673243-chromeos-test/chromeos4-row4-rack12-host15/

12/01 11:49:03.336 DEBUG|  container_bucket:0203| Test container test_159673243_1512157671_14839 is set up.
12/01 11:49:03.339 INFO |          autoserv:0215| Run command in container: /usr/local/autotest/server/autoserv -p -r /usr/local/autotest/results/159673243-chromeos-test -m chromeos4-row4-rack12-host15 -u chromeos-test -l veyron_speedy-paladin/R64-10177.0.0-rc1/bvt-cq/generic_RebootTest -s --lab True -P /usr/local/autotest/results/159673243-chromeos-test -n /usr/local/autotest/drone_tmp/attach.13920 --verify_job_repo_url --use-existing-results --pidfile-label container_autoserv
12/01 11:49:03.340 DEBUG|             utils:0212| Running 'sudo lxc-attach -P /usr/local/autotest/containers -n test_159673243_1512157671_14839 -- bash -c "/usr/local/autotest/server/autoserv -p -r /usr/local/autotest/results/159673243-chromeos-test -m chromeos4-row4-rack12-host15 -u chromeos-test -l veyron_speedy-paladin/R64-10177.0.0-rc1/bvt-cq/generic_RebootTest -s --lab True -P /usr/local/autotest/results/159673243-chromeos-test -n /usr/local/autotest/drone_tmp/attach.13920 --verify_job_repo_url --use-existing-results --pidfile-label container_autoserv"'
12/01 11:49:05.857 INFO |        server_job:0218| FAIL	----	----	timestamp=1512157745	localtime=Dec 01 11:49:05	Failed to run test inside the container: Command <sudo lxc-attach -P /usr/local/autotest/containers -n test_159673243_1512157671_14839 -- bash -c "/usr/local/autotest/server/autoserv -p -r /usr/local/autotest/results/159673243-chromeos-test -m chromeos4-row4-rack12-host15 -u chromeos-test -l veyron_speedy-paladin/R64-10177.0.0-rc1/bvt-cq/generic_RebootTest -s --lab True -P /usr/local/autotest/results/159673243-chromeos-test -n /usr/local/autotest/drone_tmp/attach.13920 --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 /usr/local/autotest/containers -n
      test_159673243_1512157671_14839 -- bash -c
      "/usr/local/autotest/server/autoserv -p -r
      /usr/local/autotest/results/159673243-chromeos-test -m
      chromeos4-row4-rack12-host15 -u chromeos-test -l veyron_speedy-
      paladin/R64-10177.0.0-rc1/bvt-cq/generic_RebootTest -s --lab True -P
      /usr/local/autotest/results/159673243-chromeos-test -n
      /usr/local/autotest/drone_tmp/attach.13920 --verify_job_repo_url --use-
      existing-results --pidfile-label container_autoserv"
  Exit status: 1
  Duration: 2.37472200394
  
  stderr:
  Traceback (most recent call last):
    File "/usr/local/autotest/server/autoserv", line 37, in <module>
      import mock
    File "/usr/local/autotest/site-packages/mock/__init__.py", line 2, in <module>
      import mock.mock as _mock
    File "/usr/local/autotest/site-packages/mock/mock.py", line 69, in <module>
      from pbr.version import VersionInfo
  ImportError: No module named pbr.version. Check logs in ssp_logs folder for more details.
 
Components: -Infra Infra>Client>ChromeOS
Labels: -Pri-2 -Build Pri-1

Comment 2 by dshi@chromium.org, Dec 2 2017

site-packages is mounted on /usr/local/autotest/site-packages inside container. The container should share the same site-packages folder with the host. So it seems that the host has some issue with missing packages. The ImportError could be raised in the host too. A simple test is to try the import in chromeos-server14.mtv:
import mock.mock as _mock
Cc: pho...@chromium.org
Owner: pho...@chromium.org
I checked the following on chromeos-server14.mtv:

cd /usr/local/autotest/site-packages
python -c 'import mock'

The mock import fails with the same exception as given in comment #0.

I'm not sure why mock isn't importable, but the easy solution would be to just not depend on mock for production code.

I'll edit the chromite.lib.cloud_trace module to remove the dependency.

Comment 6 by pho...@chromium.org, Dec 18 2017

Labels: -Pri-1 Pri-2
Status: Archived (was: Untriaged)

Sign in to add a comment