unit test nova.tests.auth_unittest.AuthTestCase.test_209_can_generate_x509 failing on Mac OS X
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Anne Gentle |
Bug Description
While setting up to do cleanup work on Nova for the pylint/pep8 blueprint, I brought down and enabled everything I could find to make the tests all function on Nova. I wrote up the components and steps, publishing in the wiki at http://
With redis, out of the box everything works *except* nova.tests.
Here's the stack trace that I receive:
[ERROR]: nova.tests.
Traceback (most recent call last):
File "/Users/
d = self._maybeInli
File "/Users/
g = f()
File "/Users/
signed_cert = X509.load_
File "/Users/
return load_cert_bio(bio, format)
File "/Users/
raise X509Error(
M2Crypto.
Digging into to the test and code a little bit, it appears that the cert_str getting returned is blank, and hence we're hitting an error when trying to use it. Under the covers, the code appears to be doing its work calling openssl directly and getting pieces back. I have 1.0.0a installed (through MacPorts) - just happened to have it. Didn't see it as an explicit dependency on anything earlier than finding it in the code.
Would be happy to help debug, but I'm very unfamiliar with both this code base and the crypto space.
-joe
I replied on IRC, but I think I missed you...
One possibility if the openssl program is not returning what you expect, is that there's little or no error checking of spawned processes. I have a patch that will hopefully get merged soon that error checks spawned processes: /code.launchpad .net/~justin- fathomdb/ nova/check- subprocess- exit-code
https:/
It might be worth trying to run the openssl command manually, or merging check-subproces s-exit- code into a copy of your branch, to see if that sheds any light on the problem...