quickstart doesn't use packaged python-tempestconf for tempest runs in CI

[Sven Anderson]

Description
===========

quickstart doesn't use the packaged python-tempestconf when running tempest in CI. That leads to the effect, that Depends-On to python-tempestconf changes don't work.

Steps to reproduce
==================

Create a tripleo-quickstart change with a Depends-On to a python-tempestconf change that triggers a ...-scenarioXXX-multinode-oooq-container CI job.

Expected result
===============
the tempest configuration is created with the packaged version of python-tempestconf created from the Depends-On change.

Actual result
=============
Another version of python-tempestconf is used.

Environment
===========
Standard CI

See https://review.openstack.org/#/c/515139/

[Arx Cruz (arxcruz)]

So, I checked, and it's working as expected, if you check your review [1] one of the job output [2] shows the Discovered services output that I added in [3], indicating that the Depends-On is getting the proper rpm package with the code.

The reason you weren't able to see the output before, was the place you put the LOG.info in your previous patch, and the way the script is called through /usr/bin/discover-tempest-config wasn't showing up the output (according Chandan Kumar).

1 - https://review.openstack.org/#/c/515139/
2 - http://logs.openstack.org/39/515139/7/check/tripleo-ci-centos-7-scenario002-multinode-oooq-container/a1a3119/logs/undercloud/home/zuul/tempest_output.log.txt.gz#_2017-12-14_15_36_33
3 - https://review.openstack.org/#/c/519714/6/config_tempest/config_tempest.py

Marking as invalid