M2Crypto installed with VirtualEnv/PIP broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Adrian Smith |
Bug Description
Fresh Nova test run on Oneiric, using virtualenv:
=======
ERROR: <nose.suite.
-------
Traceback (most recent call last):
File "/home/
self.setUp()
File "/home/
self.
File "/home/
try_
File "/home/
return func()
File "/home/
from nova.tests import fake_flags
File "/home/
flags.
File "/home/
__import_
File "/home/
from nova import crypto
File "/home/
import M2Crypto
File "/home/
import __m2crypto
ImportError: /home/jpipes/
I believe this is related to this Debian bug:
http://
Maybe we need to specify version of M2Crypto in the pip-requires file?
Changed in nova: | |
milestone: | none → essex-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
assignee: | nobody → Adrian Smith (adriansmith) |
Changed in nova: | |
milestone: | essex-2 → 2012.1 |
FWIW, on Fedora, 'pip install M2Crypto' doesn't work at all (not even for 0.20.1 or 0.20.2), so we just use the system M2Crypto package rather than installing it into venv. See the code in install_venv.py
The issue on Fedora is:
swig -python -I/usr/ include/ python2. 7 -I/usr/include -includeall -o SWIG/_m2crypto_ wrap.c SWIG/_m2crypto.i include/ openssl/ opensslconf. h:31: Error: CPP #error ""This openssl-devel package does not work your architecture?"". Use the -cpperraswarn option to continue swig processing.
/usr/
error: command 'swig' failed with exit status 1
See also:
http:// stackoverflow. com/questions/ 7772965/ m2crypto- doesnt- install- in-venv- or-swig- doesnt- define- x86-64- which-breaks /bugzilla. redhat. com/456764
https:/
A sorry tale of fail