Silently taking config value even if it is wrong in tempest run

[Manik Bindlish]

Ubuntu 16.04
Openstack/Stein

Command: tempest run
parameter: --config-file

Command is silently taking value of config, even it is wrong value.
Not raising error and some wrong value is getting assigned to config parameter which user doesn't will know about.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/625162

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/625162
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=21491dff81aa5a2448406b55ec58fff19dcf4c5f
Submitter: Zuul
Branch: master

commit 21491dff81aa5a2448406b55ec58fff19dcf4c5f
Author: Manik Bindlish <email address hidden>
Date: Fri Dec 14 06:58:42 2018 +0000

    Checking config file actually exist or not in tempest run

    This PS will check config file passed from command line is actually
    existing or not in tempest run command. If file exists, only then it
    will go for set config path otherwise will fail with value error.
    Also adding and modifying unit test cases for this change.

    Partially-Implements: blueprint tempest-cli-unit-test-coverage

    Change-Id: I09d756be69cb3a9be8d0638c41d45a089d62b238
    Closes-Bug: #1808473

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tempest 20.0.0 release.