crypto import fails on non-case sensitive filesystem

Bug #925792 reported by Vish Ishaya on 2012-02-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Vish Ishaya

Bug Description

Trying to run nova from a case insensitive filesystem gives the following traceback:

+ /opt/stack/nova/bin/nova-manage db sync
Traceback (most recent call last):
  File "/opt/stack/nova/bin/nova-manage", line 81, in <module>
    from nova import crypto
  File "/opt/stack/nova/nova/", line 34, in <module>
    import Crypto.Cipher.AES
  File "/opt/stack/nova/nova/", line 34, in <module>
    import Crypto.Cipher.AES
ImportError: No module named Cipher.AES

It interprets import Crypto as importing the local crypto instead of the global one.

Changed in nova:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Vish Ishaya (vishvananda)

Submitter: Jenkins
Branch: master

commit b863fb3744170e5aa44083fd53fa92b3b9c3fb04
Author: Vishvananda Ishaya <email address hidden>
Date: Thu Feb 2 15:24:34 2012 -0800

    Make crypto use absolute imports

     * Fixes bug 925792
     * Cleans up some extra imports as well

    Change-Id: Ibea2411f552747e074c8d2e96468e3b09bf9c9c9

Changed in nova:
status: In Progress → Fix Committed
Brian Waldon (bcwaldon) on 2012-02-02
Changed in nova:
milestone: none → essex-4
Thierry Carrez (ttx) on 2012-02-29
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-4 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers