tox: command not found on unit-test slave
Bug #1298827 reported by
Ivan Melnikov
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Core Infrastructure |
Fix Released
|
Critical
|
Jeremy Stanley | ||
Bug Description
A test job for taskflow for python 3.3 environment failed because it could not find 'tox' command.
Console log: http://
Change: https:/
Revision history for this message
| Jeremy Stanley (fungi) wrote | #1 |
| Changed in openstack-ci: | |
| status: | New → Fix Released |
| importance: | Undecided → Critical |
| assignee: | nobody → Jeremy Stanley (fungi) |
| milestone: | none → icehouse |
To post a comment you must log in.
This was related to bug 1298929. Basically the nodepool image build for this type and provider ran into...
2014-03-28 02:34:29,629 INFO nodepool.
...when trying to download tox. However it didn't abort the build, so resulting nodes from that image lacked a tox executable. I have since deleted the problem image and we've reverted to launching nodes from the previous day's image instead.