openstack
/
mistral
Code Issues Proposed changes

Fix mistral dsvm gate 

Because of https://review.openstack.org/#/c/235480/ path to
tempest conf now is defining in other way, need to export
special path and do not try to find tempest.conf using
relative path from test run directory.

Change-Id: I4de9d71332edab96e4d6c96f3b84f6ea2c459a67
This commit is contained in:
Anastasia Kuznetsova 2015-10-16 15:51:58 +03:00
parent ae0d5e9efe
commit f8087961f6
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
functionaltests/run_tests.sh
View File

@ -25,6 +25,11 @@ echo "Successfully contacted Mistral API"
# Where tempest code lives
TEMPEST_DIR=${TEMPEST_DIR:-/opt/stack/new/tempest}
# Path to directory with tempest.conf file, otherwise it will
# take relative path from where the run tests command is being executed.
export TEMPEST_CONFIG_DIR=${TEMPEST_CONFIG_DIR:-$TEMPEST_DIR/etc/}
echo "Tempest configuration file directory: $TEMPEST_CONFIG_DIR"
# Where mistral code and mistralclient code live
MISTRAL_DIR=/opt/stack/new/mistral
MISTRALCLIENT_DIR=/opt/stack/new/python-mistralclient