UUID in tempest test list

Hi

When executing a tempest case without defining a UUID for the test case, it's not executed:

root@c25f99e9d57e:~/functest/results/tempest/q2# cat test_list_no_id.txt
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
OS_TEST_LOCK_PATH=${OS_TEST_LOCK_PATH:-${TMPDIR:-'/tmp'}} \
${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} ${OS_TEST_PATH:-./tempest/test_discover} --list
tempest.api.compute.servers.test_create_server.ServersTestJSON.test_list_servers_with_detail
root@c25f99e9d57e:~/functest/results/tempest/q2#
root@c25f99e9d57e:~/functest/results/tempest/q2# rally verify start --load-list test_list_no_id.txt
2017-03-06 14:50:25.635 6837 INFO rally.api [-] Starting verification (UUID=7c488be0-20dd-4263-bbf7-4c606f3bf370) for deployment 'opnfv-rally' (UUID=d38dd198-e975-4940-8e22-d6264aa598a4) by verifier 'opnfv-tempest' (UUID=88b2ffd7-ee5d-4cc2-b521-991fa43e0944).
2017-03-06 14:50:39.188 6837 INFO rally.api [-] Verification (UUID=7c488be0-20dd-4263-bbf7-4c606f3bf370) has been successfully finished for deployment 'opnfv-rally' (UUID=d38dd198-e975-4940-8e22-d6264aa598a4)!

======
Totals
======
Ran: 0 tests in 0.000 sec.
 - Success: 0
 - Skipped: 0
 - Expected failures: 0
 - Unexpected success: 0
 - Failures: 0

Using verification (UUID=7c488be0-20dd-4263-bbf7-4c606f3bf370) as the default verification for the future operations.
root@c25f99e9d57e:~/functest/results/tempest/q2#

Same case with UUID set is executed ok:

root@c25f99e9d57e:~/functest/results/tempest/q2# cat test_list.txt
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
OS_TEST_LOCK_PATH=${OS_TEST_LOCK_PATH:-${TMPDIR:-'/tmp'}} \
${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} ${OS_TEST_PATH:-./tempest/test_discover} --list
tempest.api.compute.servers.test_create_server.ServersTestJSON.test_list_servers_with_detail[id-585e934c-448e-43c4-acbf-d06a9b899997]
root@c25f99e9d57e:~/functest/results/tempest/q2#
root@c25f99e9d57e:~/functest/results/tempest/q2# rally verify start --load-list test_list.txt
2017-03-06 14:49:26.191 6793 INFO rally.api [-] Starting verification (UUID=f526924f-a28f-4eee-9f8e-71f86607f448) for deployment 'opnfv-rally' (UUID=d38dd198-e975-4940-8e22-d6264aa598a4) by verifier 'opnfv-tempest' (UUID=88b2ffd7-ee5d-4cc2-b521-991fa43e0944).
2017-03-06 14:49:59.265 6793 INFO opnfv-tempest [-] {0} tempest.api.compute.servers.test_create_server.ServersTestJSON.test_list_servers_with_detail ... success [0.257s]
2017-03-06 14:50:11.727 6793 INFO rally.api [-] Verification (UUID=f526924f-a28f-4eee-9f8e-71f86607f448) has been successfully finished for deployment 'opnfv-rally' (UUID=d38dd198-e975-4940-8e22-d6264aa598a4)!

======
Totals
======
Ran: 1 tests in 23.167 sec.
 - Success: 1
 - Skipped: 0
 - Expected failures: 0
 - Unexpected success: 0
 - Failures: 0

Using verification (UUID=f526924f-a28f-4eee-9f8e-71f86607f448) as the default verification for the future operations.
root@c25f99e9d57e:~/functest/results/tempest/q2#

Is the UUID requirement initiated by Rally or is it coming from Tempest? I found following thread discussing similar issue but there were no real conclusion.

https://lists.linuxfoundation.org/pipermail/opnfv-users/2016-January/000433.html

Regards,
        JK