It doesn't look like tox is using it's own virtualenv
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Invalid
|
Low
|
David Moreau Simard |
Bug Description
Here's a trace when attempting to run "build-
http://
Out of curiosity, I installed testrepository globally with pip (for testr) and I then got the following trace:
http://
You can see in the stacktraces of the second paste that the python libraries used are the global ones, not the ones from the tox virtual environment.
Poking around in tox.ini, I could not find a way to fix this ?
Looking at other projects, such as Nova, you will see something like this which is missing in Kolla:
https:/
I tried to add that in, and that didn't fix it. Additional trial and error with a couple of other settings and I couldn't get it to work either.
Installing requirements and test-requirements globally works around this issue but is not really acceptable.
Changed in kolla: | |
assignee: | nobody → David Moreau Simard (dmsimard) |
status: | New → In Progress |
Changed in kolla: | |
importance: | Undecided → Low |
It looks like the culprit is sudo: /github. com/openstack/ kolla/blob/ 00b7794f3ef463c d40f1fbabefd0e3 180fd7c325/ tox.ini# L45
https:/
Surely the virutalenv settings are lost in the process.
Removing sudo from the command in an environment where the user is member of the docker group yields a successful build.
In the gate setup, instead of adding jenkins as a sudoers for the docker group, couldn't we add him to the docker group outright instead and drop the sudo from tox ?