From 0dd105221e62d5ba436a9ea8753d63f31b3f6cc6 Mon Sep 17 00:00:00 2001 From: Steve Heyman Date: Mon, 29 Jun 2015 20:19:25 -0500 Subject: [PATCH] Add troubleshooting for _bsdbb import error This import error can happen quite easily if you are running tests with different Barbican versions. Adding guidance to the documentation to help others who encounter this error. Change-Id: Ic916c042c8a5ef0cf39b4cc2f6a5ffadd9ebc29a --- doc/source/setup/troubleshooting.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/source/setup/troubleshooting.rst b/doc/source/setup/troubleshooting.rst index 55b333829..2383efb18 100644 --- a/doc/source/setup/troubleshooting.rst +++ b/doc/source/setup/troubleshooting.rst @@ -125,6 +125,22 @@ asked if you want to install the command line tools. Now tests should run. +Barbican's tox tests fail with "ImportError: No module named _bsddb" +------------------------------------------------- + +What you might see +^^^^^^^^^^^^^^^^^^ + +.. code-block:: text + + ImportError: No module named _bsddb + +How to avoid +^^^^^^^^^^^^ + +Running tests via tox (which uses testr) will create a .testrepository directory containing, among other things, data files. Those datafiles may be created with bsddb, if it is available in the environment. This can cause problems if you run in an environment that does not have bsddb. To resolve this, delete your .testrepository directory and run tox again. + + uWSGI logs 'OOPS ! failed loading app' --------------------------------------