Copy tempest.log from verify-tempest-config

As part of the current devstack runs verify-tempest-config is run to
generate a complete extension list which is only used when a disable
extension option is provided. While this is not the best method for
doing this, since it exposes the risk of silently skipping tests if
there is an api bug it is currently how devstack supports doing this.
However, calling verify-tempest-config has one side-effect that it
generates a separate log file where it's run (at least using the
default oslo logging configuration) This commit adds a check if the
log file exists and copies it along with the other artifacts. So that
people will be able to debug failures in the verify-tempest-config
tool when they occur.

Change-Id: I76c78bcf1fe49903df7d0bcecbb4c81ea0d73ca2

functions.sh

@@ -567,6 +567,9 @@ function cleanup_host {
         sudo cp $BASE/old/devstacklog.txt $BASE/logs/old/
         sudo cp $BASE/old/devstack/localrc $BASE/logs/old/localrc.txt
         sudo cp $BASE/old/tempest/etc/tempest.conf $BASE/logs/old/tempest_conf.txt
+        if -f [ $BASE/old/devstack/tempest.log ] ; then
+            sudo cp $BASE/old/devstack/tempest.log $BASE/logs/old/verify_tempest_conf.log
+        fi
 
         # grenade logs
         sudo cp $BASE/new/grenade/localrc $BASE/logs/grenade_localrc.txt
@@ -594,6 +597,9 @@ function cleanup_host {
         xargs -0 -I {} sudo cp {} $NEWLOGTARGET/
     sudo cp $BASE/new/devstacklog.txt $NEWLOGTARGET/
     sudo cp $BASE/new/devstack/localrc $NEWLOGTARGET/localrc.txt
+    if [ -f $BASE/new/devstack/tempest.log ]; then
+        sudo cp $BASE/new/devstack/tempest.log $NEWLOGTARGET/verify_tempest_conf.log
+    fi
 
     # Copy failure files if they exist
     if [ $(ls $BASE/status/stack/*.failure | wc -l) -gt 0 ]; then